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

Add description of bad rows and how to work with new bad rows in the README #25

Open
benjben opened this issue Jan 7, 2020 · 3 comments

Comments

@benjben
Copy link
Contributor

benjben commented Jan 7, 2020

Can be taken from the blog post

@benjben benjben added this to the Version 0.2.0 milestone Jan 7, 2020
@chuwy
Copy link
Contributor

chuwy commented Jan 7, 2020

Do you mean in docs or README or just in ScalaDoc?

@benjben
Copy link
Contributor Author

benjben commented Jan 7, 2020

I was thinking in the README but actually maybe we should just use sbt-ghpages and have all the information only in the Scaladoc.

@benjben benjben removed this from the Version 0.1.1 milestone Mar 10, 2020
@arthur78
Copy link

Hi guys. Are there any examples on how to use this library?

I'm checking the latest enricher and its (new) format of bad events. I took an example bad event and see it contains the alike piece of json:

"failure": { "timestamp": "2021-11-22T20:29:17.348772Z", "messages": [ { "schemaKey": "iglu:com.xxx/ui_event/jsonschema/2-0-128", "error": { "error": "ValidationError", "dataReports": [ { "message": "$.field1: does not have a value in the enumeration [option1, ...]", "path": "$.field1", "keyword": "enum", "targets": [ "[option1, ...]" ] } ] } } ] }

I understand that the provided value for that field1 is not within the list of permitted options defined by the schema, but is there an easy way for me to see the actual value provided? Can tasks like this be facilitated by that your library?

Thank you.

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

3 participants