[
https://issues.apache.org/jira/browse/LUCENE-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15517330#comment-15517330
]
ASF GitHub Bot commented on LUCENE-5317:
----------------------------------------
GitHub user tballison opened a pull request:
https://github.com/apache/lucene-solr/pull/82
First draft of LUCENE-5317
First draft of LUCENE-5317
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tballison/lucene-solr LUCENE-5317
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/lucene-solr/pull/82.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 #82
----
commit ea9fd7fdd4d94fd498f0188b9aab0c8cf48c7295
Author: tballison <talli...@mitre.org>
Date: 2016-09-23T19:19:22Z
Rough draft of LUCENE-5317.
commit 632c00980d1f7257b15b5dfde445168940dd423c
Author: tballison <talli...@mitre.org>
Date: 2016-09-23T19:20:36Z
Merge remote-tracking branch 'upstream/master' into LUCENE-5317
----
> 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
> Attachments: LUCENE-5317.patch, LUCENE-5317.patch,
> concordance_v1.patch.gz, lucene5317v1.patch, lucene5317v2.patch
>
>
> 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
