-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
serialize legacy as false for scan query for rolling downgrade/upgrade #16793
serialize legacy as false for scan query for rolling downgrade/upgrade #16793
Conversation
@@ -443,6 +443,12 @@ public List<ColumnType> getColumnTypes() | |||
return columnTypes; | |||
} | |||
|
|||
@JsonProperty("legacy") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could use a javadoc and a @Deprecated
annotation. Javadoc could be something like:
/**
* Prior to PR https://github.com/apache/druid/pull/16659 (Druid 31) data servers require
* the "legacy" parameter to be set to a non-null value. For compatibility with older data
* servers during rolling updates, we need to write out "false".
*/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added, thanks 👍
.dataSource("source") | ||
.intervals(intervalSpec) | ||
.build(); | ||
Assert.assertFalse(query.isLegacy()); |
Check notice
Code scanning / CodeQL
Deprecated method or constructor invocation Note test
ScanQuery.isLegacy
apache#16793) Fixes rolling downgrades/upgrades after apache#16659 by hard coding scan query "legacy":false since it is a required property during deserialization.
Fixes rolling downgrades/upgrades after #16659 by hard coding scan query
"legacy":false
since it is a required property during deserialization.