You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2019/03/01 16:39:00 UTC

[jira] [Commented] (SOLR-13261) Make SortableTextField work with export/streaming

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

Erick Erickson commented on SOLR-13261:
---------------------------------------

Yeah, the export writer doesn't check, and I certainly didn't put any tests in.

DV operations in general (sorting, faceting, etc) on SortableTextFields are within the constraints of the truncation of the value put in the DV. Having the same limitation apply to DV seems consistent. Whether it's right or not is what we're debating I suppose.

There are other differences, i.e. multiValued DV fields behave differently when exported than stored (deduped, sorted).

I'm not sure I like the idea of coupling the ability to export with useDocValuesAsStored. But adding a separate "useDocValuesToExport" seems like the tail wagging the dog.

The use-case here is that for an application that wanted to export a SortableTextField, you'd need to store some version of the DV twice, once in SortableTextField and once in a copyField, which for large indexes seems wasteful. Or add complexity to search on a normal text field and do everything else with a DV-only field. Seems a shame.

If a user is really concerned about this then they can set the DV portion of the SortableTextField as large as they need it to be. Would it answer to call that out LOUDLY in the docs?




> Make SortableTextField work with export/streaming
> -------------------------------------------------
>
>                 Key: SOLR-13261
>                 URL: https://issues.apache.org/jira/browse/SOLR-13261
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 7.7, 8.0, master (9.0)
>            Reporter: Erick Erickson
>            Assignee: Erick Erickson
>            Priority: Major
>             Fix For: master (9.0), 8.1
>
>         Attachments: SOLR-13261.patch, SOLR-13261.patch
>
>
> ExportWriter (and perhaps other places) explicitly tests for certain field types and error out with "Export fields must either be one of the following types: int,float,long,double,string,date,boolean"
> It seems perfectly legal to export SortableTextField as well as it's a DV field. How desirable that would be is an open question.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org