[
https://issues.apache.org/jira/browse/SOLR-18085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057636#comment-18057636
]
ASF subversion and git services commented on SOLR-18085:
--------------------------------------------------------
Commit a726e0bfed620844acf339ce6a34d684c7656a42 in solr's branch
refs/heads/branch_10x from Eric Pugh
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=a726e0bfed6 ]
SOLR-18085: Remove use of "wt=standard" internally to Solr. (#4080)
Updates Solr’s response-writer (wt) handling to remove reliance on the legacy
"standard" writer and to fail fast when an unknown response writer is
requested. Additionally we migrate from throwing a 500 error to a more
appropriate 400 error when a non existing response-write is specified.
(cherry picked from commit 4f40e977a337d440c598b6f37156045e5bd8a926)
> wt=standard isn't a helpful concept, replace with wt=json
> ---------------------------------------------------------
>
> Key: SOLR-18085
> URL: https://issues.apache.org/jira/browse/SOLR-18085
> Project: Solr
> Issue Type: Improvement
> Components: Response Writers
> Reporter: Eric Pugh
> Assignee: Eric Pugh
> Priority: Blocker
> Labels: newdev, pull-request-available
> Fix For: main(11.0), 10.1
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> The wt=standard doesnt' really help us communicate what the code is doing.
> It's just an alias for wt=json, and one we mix interchanably.
>
> If we wt=compact or wt=better or wt=super-awesome then I might see using this
> as a concept.
>
> today wt=standard just makes things more confusing.
>
> We should go through where wt=standard is used and swap it to wt=json.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
