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

Ensure Stream Enrich resolver uses cacheTtl of one #137

Closed
jbeemster opened this issue Nov 2, 2017 · 6 comments
Closed

Ensure Stream Enrich resolver uses cacheTtl of one #137

jbeemster opened this issue Nov 2, 2017 · 6 comments
Assignees
Milestone

Comments

@jbeemster
Copy link
Member

cc/ @alexanderdean

@alexanderdean
Copy link
Member

Need to think about this one as in theory a user can control the whole Iglu resolver file, but we want to encourage using one with a zero cacheTtl...

@alexanderdean
Copy link
Member

0.4.0 was already in progress, assigning to 0.5.0

@alexanderdean
Copy link
Member

Bringing forwards.

@oguzhanunlu
Copy link
Member

@alexanderdean @chuwy There is an issue with using cacheTtl of 0.

resolver-config 1-0-2 indicates cacheTtl can be at least 1. If we definitely want to use 0, we need to add a new schema to iglu-central but in this case iglu scala client would not recognize since its resolver is based on 1-0-2.

Would using cacheTtl of 1 be any problem?

@chuwy
Copy link

chuwy commented Apr 27, 2018

I think regardless of this ticket, we should add 1-0-3 schema to Iglu Central and create a ticket in iglu client to loosen config's criterion.

@alexanderdean
Copy link
Member

Agree, thanks.

@oguzhanunlu oguzhanunlu mentioned this issue May 2, 2018
14 tasks
@oguzhanunlu oguzhanunlu changed the title Ensure Stream Enrich resolver uses cacheTtl of zero Ensure Stream Enrich resolver uses cacheTtl of one May 2, 2018
@oguzhanunlu oguzhanunlu mentioned this issue May 30, 2018
18 tasks
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

5 participants