[ 
https://issues.apache.org/jira/browse/SOLR-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132150#comment-18132150
 ] 

Nick Shanin commented on SOLR-7070:
-----------------------------------

>From code reading against apache/main b73f03976fa, the reference guide says 
>field names should not start with a digit 
>(solr/solr-ref-guide/modules/indexing-guide/pages/fields.adoc:43), and fl 
>reads a plain field name only when it starts with an identifier character 
>(solr/core/src/java/org/apache/solr/search/SolrReturnFields.java:225-229). 
>[~kgalal], if you see a real defect on a supported release, reply and I will 
>reopen it. Otherwise I plan to close it as not a bug.

🤖 AI-generated 🤖

> Issue when using "fl" with field names that start with numbers
> --------------------------------------------------------------
>
>                 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
>            Priority: Major
>              Labels: dynamic, fields
>
> field names starting with numbers aren't working properly in fl, specific 
> example from original bug report related to dynamic field suffixes using a 
> numeric prefix...
> ----
> 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
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to