Error with Stream Enrich using Iglu Server


#1

Hi all,
I’m getting this error with my stream enrichments, using a self-hosted iglu server (on docker):

"errors":[{"level":"error","message":"error: Could not find schema with key iglu:com.mycompany/schema_name/jsonschema/1-0-0 in any repository, tried: ...

My resolver.json, using an internal uri for the iglu server:

{
  "schema": "iglu:com.snowplowanalytics.iglu/resolver-config/jsonschema/1-0-1",
  "data": {
    "cacheSize": 1000,
    "repositories": [
      {
        "name": "Iglu Central",
        "priority": 0,
        "vendorPrefixes": [ "com.snowplowanalytics" ],
        "connection": {
          "http": {
            "uri": "http://iglucentral.com"
          }
        }
      },
      {
        "name": "Iglu Central - GCP Mirror",
        "priority": 1,
        "vendorPrefixes": [ "com.snowplowanalytics" ],
        "connection": {
          "http": {
            "uri": "http://mirror01.iglucentral.com"
          }
        }
      },
      {
        "name": "Custom Iglu Repo 1",
        "priority": 5,
        "vendorPrefixes": [ "com.mycompany" ],
        "connection": {
          "http": {
            "uri": "http://my.local.hostname:8080"
          }
        }
      }
    ]
  }
}

I’ve also configured the resolver.json to use the external uri for the iglu server, “https://iglu.myurl.com” and get the same error. The ports are configured correctly, which I can confirm since the url below for the public api is functioning properly.

The iglu server is working, and the schemas are all public, which I can verify by opening this url in a browser and seeing the JSON output for all schemas:
https://iglu.myurl.com/api/schemas/public

However, I cannot access the individual schemas via web browser using urls like these:
https://iglu.myurl.com/schemas/my_schema/jsonschema/1-0-0
https://iglu.myurl.com/my_schema/jsonschema/1-0-0
as I get this response:
The requested resource could not be found.

What am I missing?


#2

Hi @rob-- I just hit this issue myself. Did you ever figure out what was going wrong?


#3

@pearsonhenri I haven’t yet found a solution or what the issue is. If you find anything, please report back as I’d like to fix this.


#4

Yo, so it might be the issue referred to in this GitHub comment: https://sea-region.github.com/snowplow/snowplow/issues/3845#issuecomment-408454698

(basically just add /api to the endpoint for your self-hosted Iglu server)


#5

Thanks! Is that fix working for you? I will test it eventually, but can’t for some time.


#6

Yup, it’s working for me! I’m wondering if the /api bit is referenced somewhere in the docs however. This GitHub comment was the only place I could find it.