[ https://issues.apache.org/jira/browse/SOLR-14454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17100429#comment-17100429 ]
Michael Gibney commented on SOLR-14454: --------------------------------------- Thanks for taking a closer look! And yes I'm perfectly happy to abandon the compression aspect altogether, esp. with hooks there to provide it as a plugin if desired (indeed I was kind of anticipating that, part of why I separated it out into its own commit). {quote}Nonetheless I want to ensure that the chosen solution is a workable basis for both use-cases. {quote} That sounds great, however you think it might make sense to proceed. > support for UTF-8 (string) types with DocValuesType.BINARY > ---------------------------------------------------------- > > Key: SOLR-14454 > URL: https://issues.apache.org/jira/browse/SOLR-14454 > Project: Solr > Issue Type: New Feature > Security Level: Public(Default Security Level. Issues are Public) > Components: Schema and Analysis > Affects Versions: master (9.0) > Reporter: Michael Gibney > Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > The goal is to add support for string fields with arbitrarily large values in > the {{/export}} handler and streaming expressions. > {{StrField}} values are currently limited to 32766 bytes for the case where > {{indexed=true}} or {{docValues=true}}. Exceeding this value triggers an > "immense field" warning, and causes indexing to fail for the associated input > doc. > Configuring a {{StrField}} field as "{{indexed=false docValues=false}}" > removes this size limitation, so it is already possible to have large > _stored_ {{StrField}} values. But the "{{docValues=true}}" prerequisite for > the {{/export}} handler (and consequently for streaming expressions) limits > the size of field that can be used in conjunction with these features. > Adding support for UTF-8/string field types with {{DocValuesType.BINARY}} > would address this limitation and allow considerable flexibility in the > implementation of custom field types. N.b.: this would address field value > retrieval use cases only (e.g., {{/export}} and {{useDocValuesAsStored}}); > neither sorting nor faceting would be supported. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org