[jira] [Updated] (LUCENE-5317) [PATCH] Concordance capability

["Steve Rowe (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LUCENE-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Rowe updated LUCENE-5317:
-------------------------------
    Attachment: LUCENE-5317.patch

Sync'd Tim's patch up to current trunk:

- LUCENE-5449: _TestUtil->TestUtil
- LUCENE-5569 AtomicReader->LeafReader
- LUCENE-5984: ChainedFilter removed; replaced with BooleanFilter
- LUCENE-6010: OpenBitSet removed; replaced with FixedBitSet, except for in TokenCharOffsetRequests, where I switched it to Java's BitSet.
- Added Maven and IntelliJ config
- Cleaned up some code formatting issues:
-- indents -> 2 spaces per level
-- removed useless javadoc stuff (empty returns, empty params)
-- normalized whitespace
-- normalized curly brace placement
-- removed unused imports
-- converted some counted for loops to for-each

I left a few nocommits.

I plan on reviewing more.

> [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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org