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

ASF GitHub Bot commented on JENA-1630:
--------------------------------------

GitHub user xristy opened a pull request:

    https://github.com/apache/jena/pull/489

    Merged store literals once for JENA-1630

    Store literals only once per Lucene document for multilingual jena-text 
configurations. Include lucene-backward-codecs dependency for jena/fuseki 
installs with Lucene indexes older than Lucene 7.x

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/BuddhistDigitalResourceCenter/jena 
JENA-1630-store-literals-once

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/jena/pull/489.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #489
    
----
commit d12919e3e4c849ddec2ada4af08cc5afe04cf4f6
Author: Code Ferret <codeferret@...>
Date:   2018-11-14T15:31:11Z

    Merged ReduceLuceneIndex

----


> store literals only once in lucene docs for jena-text w/ multilingual configs
> -----------------------------------------------------------------------------
>
>                 Key: JENA-1630
>                 URL: https://issues.apache.org/jira/browse/JENA-1630
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Text
>    Affects Versions: Jena 3.9.0
>            Reporter: Code Ferret
>            Assignee: Code Ferret
>            Priority: Major
>              Labels: easyfix, performance, pull-request-available
>             Fix For: Jena 3.10.0
>
>
> We can save some space in the Lucene db for jena-text when using multilingual 
> configurations by only storing the incoming literal once rather than for each 
> field's language tag variant.
> A PR is ready



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

Reply via email to