[ https://issues.apache.org/jira/browse/SOLR-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761725#action_12761725 ]
Yonik Seeley commented on SOLR-1478: ------------------------------------ A Lucene field name can be anything... so '#' could also be a collision. If we wish to reserve certain names going forward, I'd vote for reserving ids with an underscore on either side. But really, the whole collision thing is overblown... this is a single name that people will not have used before. On a practical level, I don't believe it's an issue. We will need another one too - as a container for document metadata. I've suggested _meta_ for that in SOLR-705. We aren't adding these all the time... there was exactly one before this.. "score". No future document level metadata will collide since they will be contained in whatever _meta_ ends up being. Further advantages to __id__ (single underscores surrounding the id): - consistent with magic fieldnames __query__ and __val__ for nested queries in the query parser, and I could see supporting __id__:1 in the future - people *may* want to return the actual ids for documents... wherever that info goes (separate return vector like sort_field_values for distributed search or __meta__) it will be nicer for clients if the label for it is actually an identifier and not '#' > Enable sort by docid > -------------------- > > Key: SOLR-1478 > URL: https://issues.apache.org/jira/browse/SOLR-1478 > Project: Solr > Issue Type: New Feature > Components: search > Reporter: Erik Hatcher > Priority: Minor > Fix For: 1.4 > > Attachments: SOLR-1478.patch > > > Lucene allows sorting by docid, but Solr currently does not provide a way to > specify it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.