Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EventHub Source processor properties not populating #1298

Open
kphwx opened this issue Jun 25, 2018 · 6 comments
Open

EventHub Source processor properties not populating #1298

kphwx opened this issue Jun 25, 2018 · 6 comments

Comments

@kphwx
Copy link

kphwx commented Jun 25, 2018

When configuring an Event Hub processor, the values of Schema Branch/Version show "results not found" despite entering valid values for all previous parameters (username, passwd, namespace, entitypath).

Expecting the Schema Branch to read from Schema Registry and show "MASTER" (default) as branch but it appears that the Processor isn't syncing these values properly from schema registry?

screen shot 2018-06-25 at 7 06 06 pm

screen shot 2018-06-25 at 7 05 42 pm

@arunmahadevan
Copy link
Contributor

For eventhubs, SAM looks up schema based on the value entered in "Entity path" . In this case you need to define a schema with name "woolies" (not testeventhub).

@kphwx
Copy link
Author

kphwx commented Jul 19, 2018

@arunmahadevan thanks for checking this out.

I did actually have a schema named "woolies" as well which i've tried again now.

I think it's validating that OK - doesn't give error "schema not found" when you enter woolies - but then no values are populated into SCHEMA BRANCH.

screen shot 2018-07-20 at 9 30 57 am

@arunmahadevan
Copy link
Contributor

@kphwx, you might want to check if the streamline and registry versions are compatible. From the screenshot it appears so. You could also enable debug logs for streamline and schema registry and see the request/response being sent.

This works for me with the latest version of streamline/registry (master branch).

@kphwx
Copy link
Author

kphwx commented Jul 20, 2018

@arunmahadevan the SAM I have with HDF 3.1.2 seems to be version 0.6.0. However, SR is 0.5.1 which is interesting as the component notes for HDF say SR is listed as 0.5.0.

Is yours 0.5.0?

Also, looking at output withe DEBUG on (thanks for that suggestion) it looks like it's calling a different GET api method than what is in swagger? See output below or file
streamline.log-error.txt

Looking the swagger docs it should be calling: /api/v1/schemaregistry/schemas??

INFO [2018-07-20 01:21:26.639] [dw-27 - GET /api/v1/schemas/woolies/versions] c.h.s.s.s.SchemaResource - Get all versions for schema : woolies
INFO [2018-07-20 01:21:45.370] [dw-40 - GET /api/v1/schemas/undefined/versions/1] c.h.s.s.s.SchemaResource - Get schema:version undefined:1
INFO [2018-07-20 01:21:45.372] [dw-40 - GET /api/v1/schemas/undefined/versions/1] c.h.r.s.c.SchemaVersionInfoCache - Loading entry for cache with key [Key {schemaVersionKey=SchemaVersionKey{schemaName='undefined', version=1}, schemaIdVersion=null}] from target service
INFO [2018-07-20 01:21:45.372] [dw-40 - GET /api/v1/schemas/undefined/versions/1] c.h.r.s.c.SchemaRegistryClient - Getting schema version from target registry for [SchemaVersionKey{schemaName='undefined', version=1}]
ERROR [2018-07-20 01:21:45.412] [dw-40 - GET /api/v1/schemas/undefined/versions/1] c.h.s.s.s.SchemaResource - Got exception: [RuntimeException] / message [java.lang.RuntimeException: com.google.common.util.concurrent.UncheckedExecutionException: javax.ws.rs.NotFoundException: HTTP 404 Not Found] / related resource location: com.hortonworks.streamline.streams.service.SchemaResource.getSchemaForVersion
java.lang.RuntimeException: java.lang.RuntimeException: com.google.common.util.concurrent.UncheckedExecutionException: javax.ws.rs.NotFoundException: HTTP 404 Not Found

@arunmahadevan
Copy link
Contributor

If you are using HDF 3.1.2 I am not sure how are you even getting the "Schema Branch" option in the UI because the changes for that have not gone into HDF-3.1-maint.

See - #1240

This has been fixed in master and should be available in the next release (HDF 3.2 or streamline 0.7).

@kphwx
Copy link
Author

kphwx commented Jul 20, 2018

@arunmahadevan

Hmmm. OK, not sure what is happening there.

Should I use the prior HDF version (3.1.1) instead?

screen shot 2018-07-20 at 12 56 21 pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants