Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.6
    • Fix Version/s: 1.6.1
    • Component/s: o.c.jsword.book
    • Labels:
      None

      Description

      Lucene 2.9 has been released with significant improvements.
      Part of the impact will require a change to PassageTally to know the total number of hits but store only the top hits.

      Further improvements have been made to 3.0.3. And the soon to be released 3.1 improves handling of utf-8 modules.

        Attachments

          Activity

          Hide
          qmx Douglas Campos added a comment -

          we're at lucene 3.5.0, wouldn't it be a better target?

          Show
          qmx Douglas Campos added a comment - we're at lucene 3.5.0, wouldn't it be a better target?
          Hide
          dmsmith DM Smith added a comment -

          3.5 would be better, but 3.6 due out very soon, would be better.

          I've started the work, but it is not trivial. Every user index would need to be rebuilt, too.

          Show
          dmsmith DM Smith added a comment - 3.5 would be better, but 3.6 due out very soon, would be better. I've started the work, but it is not trivial. Every user index would need to be rebuilt, too.
          Hide
          dmsmith DM Smith added a comment -

          Lucene 3.6 will be out shortly.

          Show
          dmsmith DM Smith added a comment - Lucene 3.6 will be out shortly.
          Hide
          qmx Douglas Campos added a comment -

          Are you using a branch for it?

          Show
          qmx Douglas Campos added a comment - Are you using a branch for it?
          Hide
          dmsmith DM Smith added a comment -

          No public branch. It is local to my machine. For SVN, I've found it easy to have multiple checkouts of trunk and separate my work that way. Far from ideal, and thus the now serious thought of moving to git.

          Show
          dmsmith DM Smith added a comment - No public branch. It is local to my machine. For SVN, I've found it easy to have multiple checkouts of trunk and separate my work that way. Far from ideal, and thus the now serious thought of moving to git.

            People

            • Assignee:
              dmsmith DM Smith
              Reporter:
              dmsmith DM Smith
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: