You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jena.apache.org by xristy <gi...@git.apache.org> on 2018/11/05 20:59:31 UTC

[GitHub] jena pull request #488: Merged Lucene upgrade. This resolves JENA-1621

GitHub user xristy opened a pull request:

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

    Merged Lucene upgrade. This resolves JENA-1621

    Updates ``jena-text`` and ``jena-text-es`` to **Lucene 7.4.0** and **ElasticSearch 6.4.2**

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

    $ git pull https://github.com/BuddhistDigitalResourceCenter/jena JENA-1621-Lucene-7.4.0

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

    https://github.com/apache/jena/pull/488.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 #488
    
----
commit 63525085be7927567a8d963586b15269416e1b90
Author: Code Ferret <co...@...>
Date:   2018-11-05T20:56:14Z

    Merged Lucene upgrade. This resolves JENA-1621

----


---

[GitHub] jena pull request #488: Merged Lucene upgrade. This resolves JENA-1621

Posted by afs <gi...@git.apache.org>.

Github user afs commented on a diff in the pull request:

    https://github.com/apache/jena/pull/488#discussion_r231081048
  
    --- Diff: jena-text-es/pom.xml ---
    @@ -140,12 +140,13 @@
             <groupId>com.github.alexcojocaru</groupId>
             <artifactId>elasticsearch-maven-plugin</artifactId>
             <!-- REPLACE THE FOLLOWING WITH THE PLUGIN VERSION YOU NEED -->
    -        <version>5.2</version>
    +        <version>6.8</version>
             <configuration>
               <clusterName>elasticsearch</clusterName>
               <transportPort>9500</transportPort>
               <httpPort>9400</httpPort>
               <timeout>${es.startup.timeout}</timeout>
    +          <version>6.4.2</version>
    --- End diff --
    
    Can this be the property ver.elasticsearch?


---

[GitHub] jena issue #488: Merged Lucene upgrade. This resolves JENA-1621

Posted by ajs6f <gi...@git.apache.org>.

Github user ajs6f commented on the issue:

    https://github.com/apache/jena/pull/488
  
    I've seen that happen when I've forgotten to rebase over master before merging, but I don't know if that's what's happening here...


---

[GitHub] jena pull request #488: Merged Lucene upgrade. This resolves JENA-1621

Posted by asfgit <gi...@git.apache.org>.

Github user asfgit closed the pull request at:

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


---

[GitHub] jena issue #488: Merged Lucene upgrade. This resolves JENA-1621

Posted by xristy <gi...@git.apache.org>.

Github user xristy commented on the issue:

    https://github.com/apache/jena/pull/488
  
    I'm not sure how I ended up w/ _unmerged commits_. All of the changes appear in apache jena git repo and github jena git repo so all looks consistent to me other than the message.


---