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

SOLR-17494: Remove language specific writer types #2758

Merged
merged 14 commits into from
Oct 21, 2024

Conversation

epugh
Copy link
Contributor

@epugh epugh commented Oct 11, 2024

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.

QueryResponseWriter w = new PythonResponseWriter();
QueryResponseWriter w = new JSONResponseWriter();
new StringWriter();
StringWriter buf;
Copy link
Contributor

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();

Copy link
Contributor

@gerlowskija gerlowskija left a 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?)

@epugh
Copy link
Contributor Author

epugh commented Oct 13, 2024

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 @deprecated in the branch_9x branch?

@janhoy
Copy link
Contributor

janhoy commented Oct 14, 2024

Deprecate as notice in ref guide. Also we have a separate deprecation logging mechanism.

@epugh
Copy link
Contributor Author

epugh commented Oct 15, 2024

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 branch_9x.....

@epugh
Copy link
Contributor Author

epugh commented Oct 18, 2024

Can I get a LGTM and then I'll add CHANGES.txt and merge....

@epugh epugh merged commit 018e4f4 into apache:main Oct 21, 2024
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants