-
Notifications
You must be signed in to change notification settings - Fork 658
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
SOLR-17494: Remove language specific writer types #2758
Conversation
QueryResponseWriter w = new PythonResponseWriter(); | ||
QueryResponseWriter w = new JSONResponseWriter(); | ||
new StringWriter(); | ||
StringWriter buf; |
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.
[-1] I think L60-L61 is a typo and should be the single line:
StringWriter buf = new StringWriter();
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.
One test-side typo that needs fixed, but when that's fixed this LGTM.
Oh, and maybe this should have a 10.0 CHANGES.txt entry? (Or maybe two entries - one for 9.8 to signal the deprecation, and one for 10.0 to announce the removal?)
Thoughts on how to mark it "deprecated" in 9x? In some places it makes sense to put out a log message. What would being deprecated mean here? Just a PR that adds |
Deprecate as notice in ref guide. Also we have a separate deprecation logging mechanism. |
Cool.. So I will open a seperate PR that does those two things only in |
Can I get a LGTM and then I'll add CHANGES.txt and merge.... |
https://issues.apache.org/jira/browse/SOLR-17494
Description
Language specific writers types are "evaled" which isn't secure. And not a pattern to be used.
Solution
Remove them from main.