[
https://issues.apache.org/jira/browse/SOLR-18483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18138016#comment-18138016
]
Jason Gerlowski commented on SOLR-18483:
----------------------------------------
bq. or is it enough to treat it like any other parameter like "&foobar=true"?
It'd be nice to at least warn on this, so that folks can catch the mistake.
That feels like the best way to achieve "principle of least surprise" here, and
we've done it for other high-profile deprecations in the past I believe.
> Prevent wt= parameter from working in V2 land
> ---------------------------------------------
>
> Key: SOLR-18483
> URL: https://issues.apache.org/jira/browse/SOLR-18483
> Project: Solr
> Issue Type: Sub-task
> Components: v2 API
> Affects Versions: 10.0
> Reporter: Eric Pugh
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> wt=xml etc works on v2 apis as a bit of "muscle memory", but honestly, I
> don't think we should support v1 concepts in v2 thaqt we don't plan on
> keeping. It's just setting us up for errors, misunderstanding, and
> eventually a surprise. Let's remove it now.
> Do we think this parameter needs to actually raise an error if used in a v2?
> or is it enough to treat it like any other parameter like "&foobar=true"?
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
