[
https://issues.apache.org/jira/browse/SOLR-10286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929055#comment-15929055
]
ASF subversion and git services commented on SOLR-10286:
--------------------------------------------------------
Commit 4628cf478373faa6116bf6e41e04337d71db2e9d in lucene-solr's branch
refs/heads/branch_6x from [~dsmiley]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=4628cf4 ]
SOLR-10286: fix test; we were writing to read-only dir.
Expand solrconfig-managed-schema.xml to have toggle-able elements vis system
property flags
(cherry picked from commit 4ee7fc3)
> Declare a field as "large", don't keep value in the document cache
> ------------------------------------------------------------------
>
> Key: SOLR-10286
> URL: https://issues.apache.org/jira/browse/SOLR-10286
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Assignee: David Smiley
> Fix For: 6.5
>
> Attachments: SOLR-10286_large_fields.patch,
> SOLR-10286_large_fields.patch
>
>
> (part of umbrella issue SOLR-10117)
> This adds a field to be declared as "large" in the schema. In the
> {{SolrIndexSearcher.doc(...)}} handling, these fields are lazily fetched from
> Lucene. Unlike {{LazyDocument.LazyField}}, it's not cached after first-use
> unless the value is "small" < 512KB by default. "large" can only be used
> when its stored="true" and multiValued="false" and the field is otherwise
> compatible (basically not a numeric field) -- you'll get a helpful exception
> if it's unsupported. BinaryField is not yet supported at this time; it could
> be in the future.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
