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

Prepare For Partial Data V2 #264

Merged
merged 7 commits into from
May 9, 2017
Merged

Prepare For Partial Data V2 #264

merged 7 commits into from
May 9, 2017

Conversation

QubitPi
Copy link
Contributor

@QubitPi QubitPi commented May 2, 2017

1st PR implementing #215

@@ -124,6 +124,9 @@ bard__default_asyncAfter=never
# Flag to turn on case sensitive keys in keyvalue store
bard__case_sensitive_keys_enabled = false

# Default value for Druid limit on uncovered interval
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is obviously the default because it's in this file. Instead, the comment should describe what the parameter is for, what it controls, and what this default value means or does.

TOO_MUCH_INTERVAL_MISSING(
"More than %s interval missing information received from druid, inspect if query " +
"expects more than %s missing intervals or increase " +
"uncoveredIntervalsLimit configuration value\n"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is there a newline character here?

@@ -42,3 +42,6 @@ bard__top_n_enabled=true

# Flag to turn on case sensitive keys in keyvalue store
bard__case_sensitive_keys_enabled = false

# Default value for Druid limit on uncovered interval
bard__druid_uncovered_interval_limit = -1
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This shouldn't be needed, the module config (where the default is specified) should be being used.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still needs addressing I think?

@@ -66,3 +66,6 @@ bard__intersection_reporting_enabled = false

# Flag to turn on case sensitive keys in keyvalue store
bard__case_sensitive_keys_enabled = false

# Default value for Druid limit on uncovered interval
bard__druid_uncovered_interval_limit = -1
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This shouldn't be needed, the module config (where the default is specified) should be being used.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cdeszaq @garyluoex I dropped it. But let me know if it needs to be kept and I can put it back at anytime.

@@ -41,3 +41,6 @@ bard__top_n_enabled=true

# Flag to turn on case sensitive keys in keyvalue store
bard__case_sensitive_keys_enabled = false

# Default value for Druid limit on uncovered interval
bard__druid_uncovered_interval_limit = -1
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This shouldn't be needed, the module config (where the default is specified) should be being used.

@QubitPi QubitPi force-pushed the prepare-for-partial-data-v2 branch from 1cfd34f to 80325d6 Compare May 3, 2017 19:59
@garyluoex garyluoex self-assigned this May 4, 2017
Copy link
Collaborator

@garyluoex garyluoex left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need Change Log

@@ -36,7 +37,8 @@
USE_CACHE("useCache"),
POPULATE_CACHE("populateCache"),
BY_SEGMENT("bySegment"),
FINALIZE("finalize");
FINALIZE("finalize"),
UNCOVERED_INTERVALS_LIMIT("uncoveredIntervalsLimit");
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

put the semicolon to the next line.

@@ -63,6 +63,3 @@ bard__default_per_page = 10000

# Intersection reporting enabled or not.
bard__intersection_reporting_enabled = false

# Flag to turn on case sensitive keys in keyvalue store
bard__case_sensitive_keys_enabled = false
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this being removed here? Does this have anything to do with the rest of the changes in this PR?

@@ -42,3 +42,6 @@ bard__top_n_enabled=true

# Flag to turn on case sensitive keys in keyvalue store
bard__case_sensitive_keys_enabled = false

# Default value for Druid limit on uncovered interval
bard__druid_uncovered_interval_limit = -1
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still needs addressing I think?

CHANGELOG.md Outdated
@@ -9,6 +9,8 @@ Current
-------
### Added:

- [Prepare For Partial Data V2](https://github.com/yahoo/fili/pull/264)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

list things like, added more error message, added new feature flag, added new queryContext

Copy link
Collaborator

@garyluoex garyluoex left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After change log update

@@ -124,6 +124,9 @@ bard__default_asyncAfter=never
# Flag to turn on case sensitive keys in keyvalue store
bard__case_sensitive_keys_enabled = false

# Sets the upper limit of the number of Druid uncovered interval. Default is -1 meaning no uncovered interval is allowed
bard__druid_uncovered_interval_limit = -1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't 0 be just as good for 'no uncovered interval'?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@michael-mclawhorn @cdeszaq @garyluoex I vote for 0 but I'm open to either

Copy link
Collaborator

@garyluoex garyluoex May 5, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets change it to 0, I was thinking something that doesn't work. Change all check for partial data v2 enabled to be strictly greater than 0 also.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@garyluoex @michael-mclawhorn I have changed it to 0. #267 has been update as well.

@michael-mclawhorn
Copy link
Contributor

I'm a little unclear on what the value of a counter for number of uncovered intervals is. How is a count of intervals meaningful from a correctness perspective?

@garyluoex
Copy link
Collaborator

The count is required by druid to turn the feature on, at the same time limiting the total header size.

@cdeszaq cdeszaq merged commit 8e3d7f4 into master May 9, 2017
@cdeszaq cdeszaq deleted the prepare-for-partial-data-v2 branch May 10, 2017 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants