[
https://issues.apache.org/jira/browse/SOLR-7314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009356#comment-16009356
]
Jason Gerlowski commented on SOLR-7314:
---------------------------------------
I think this is worth doing. When users are forced to create their own
constants, they miss out on deprecation warnings when features/parameters
they're using are sunset.
Going to push a patch up for this shortly.
Does anyone know of any other parameter constants missing from SolrJ that we
can add as a part of this patch? This report is a few years old, and as Simon
mentioned, there were likely others even back then.
> Constants missing in Solrj
> --------------------------
>
> Key: SOLR-7314
> URL: https://issues.apache.org/jira/browse/SOLR-7314
> Project: Solr
> Issue Type: Wish
> Components: SolrJ
> Reporter: Simon Endele
>
> There are some parameter names/values, for which constants are missing in
> SolrJ. One has always to declare constants for them by herself (or hard-code
> them).
> * "defType"
> * "edismax" (value for defType)
> * "dismax" (value for defType)
> * "lucene" (value for defType)
> * "spellcheck" (there's SpellingParams.SPELLCHECK_PREFIX = "spellcheck.", but
> none without dot)
> * "[elevated]" (pseudo field for the QueryElevationComponent)
> See http://lucene.apache.org/solr/5_0_0/solr-solrj/constant-values.html
> Maybe there are even more, but these are the ones I always stumble upon.
> Of course there are constants in the Solr Core code, but typically one
> doesn't want to have a dependency on it when implementing a client.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
