[
https://issues.apache.org/jira/browse/LUCENE-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175274#comment-14175274
]
Steve Rowe commented on LUCENE-5317:
------------------------------------
Tim, FYI, I've used the ASF's ReviewBoard instance a few times recently - it's
very nice for comparing two patches against each other, and it can be useful
for detailed review too: https://reviews.apache.org/. After creating an
account there, the workflow is: manually upload a patch, assign a reviewer
(could be the "lucene" group, in which case review requests go to the dev list,
or a RB account-holder, including yourself), then publish. Thereafter anybody
can review by clicking on one or more adjacent lines in a patch and attaching a
comment, repeating till done, then publishing, and the original review request
creator can update the patch, and anybody can view differences between any two
patched versions, and also attach reviews to the patched version differences.
> [PATCH] Concordance capability
> ------------------------------
>
> Key: LUCENE-5317
> URL: https://issues.apache.org/jira/browse/LUCENE-5317
> Project: Lucene - Core
> Issue Type: New Feature
> Components: core/search
> Affects Versions: 4.5
> Reporter: Tim Allison
> Labels: patch
> Fix For: 4.9
>
> Attachments: LUCENE-5317.patch, concordance_v1.patch.gz
>
>
> This patch enables a Lucene-powered concordance search capability.
> Concordances are extremely useful for linguists, lawyers and other analysts
> performing analytic search vs. traditional snippeting/document retrieval
> tasks. By "analytic search," I mean that the user wants to browse every time
> a term appears (or at least the topn) in a subset of documents and see the
> words before and after.
> Concordance technology is far simpler and less interesting than IR relevance
> models/methods, but it can be extremely useful for some use cases.
> Traditional concordance sort orders are available (sort on words before the
> target, words after, target then words before and target then words after).
> Under the hood, this is running SpanQuery's getSpans() and reanalyzing to
> obtain character offsets. There is plenty of room for optimizations and
> refactoring.
> Many thanks to my colleague, Jason Robinson, for input on the design of this
> patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
