[
https://issues.apache.org/jira/browse/JENA-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689814#comment-16689814
]
ASF GitHub Bot commented on JENA-1630:
--------------------------------------
Github user xristy commented on the issue:
https://github.com/apache/jena/pull/489
Thanks Andy.
I see now that I haven't been pulling the PR from github. I just need to
replace steps 11-12 & 14 above by:
11) ``git pull github-jena pull/489/head --no-ff`` w/ the appropriate
comment info
and then continue w/ testing and the push to ``apache-jena``.
The [Commit Workflow
page](https://cwiki.apache.org/confluence/display/JENA/Commit+Workflow+for+Github-ASF)
is silent about what _local_ branch should be used, but it seems that master
would be appropriate.
I was referring to the _Closed message_ at the bottom of the PR page just
below the last comment
> 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)
