[
https://issues.apache.org/jira/browse/SOLR-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303990#comment-14303990
]
Hoss Man commented on SOLR-7070:
--------------------------------
Can you please provide more details about your schema, your request URLs, and
the exact behavior you are seeing?
I just used Solr 4.10.3 along with the default example...
{noformat}
bin/solr start -e default
cd example/exampledocs/
java -jar post.jar *.xml
{noformat}
and had no problem getting fl to work with a field name generated from a
dynamicField...
{noformat}
curl
'http://localhost:8983/solr/select?q=manu:belkin&fl=manu_id_s&wt=json&indent=true'
{
"responseHeader":{
"status":0,
"QTime":1,
"params":{
"fl":"manu_id_s",
"indent":"true",
"q":"manu:belkin",
"wt":"json"}},
"response":{"numFound":2,"start":0,"docs":[
{
"manu_id_s":"belkin"},
{
"manu_id_s":"belkin"}]
}}
{noformat}
> Issue when using "fl" with dynamic filelds without setting wilcards
> -------------------------------------------------------------------
>
> Key: SOLR-7070
> URL: https://issues.apache.org/jira/browse/SOLR-7070
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.10.3
> Reporter: Khalid Galal
> Labels: dynamic, fields
> Fix For: 4.6
>
>
> Issue when using "fl" with dynamic fields without setting wildcards, such as:
> In solr 4.6, I used to select dynamic fields by exact match, e.g. the below
> query used to work with me:
> fl=123_PART
> But in solr 4.10.3, the above query doesn't work any more, so I am forced to
> use a wildcards, such as to be begin with match, e.g. the below query:
> fl=*_PART
> The above query works but returns all dynamic fields that end with "_PART",
> and that results in bad performance as our dynamic fields are stored.
> Is there any way to be able to select a dynamic field exactly like in version
> 4.6?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]