[
https://issues.apache.org/jira/browse/LUCENE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-2294:
---
Attachment: LUCENE-2294.patch
Patch with applied comments. I'll start moving the code to use the new
[
https://issues.apache.org/jira/browse/LUCENE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842176#action_12842176
]
Shai Erera commented on LUCENE-2294:
bq. Hmm... I think we should still allow package
[
https://issues.apache.org/jira/browse/LUCENE-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2298:
Attachment: stemmer_2.7z
tables that must go in the resources folder under Polish (o.a.l.analy
[
https://issues.apache.org/jira/browse/LUCENE-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2298:
Attachment: LUCENE-2298.patch
Attached is an initial patch. i made the following changes to the or
Polish Analyzer
---
Key: LUCENE-2298
URL: https://issues.apache.org/jira/browse/LUCENE-2298
Project: Lucene - Java
Issue Type: New Feature
Components: contrib/analyzers
Affects Versions: 3.1
Reporter: Ro
On Fri, Mar 5, 2010 at 10:00 PM, Michael McCandless
wrote:
> On Fri, Mar 5, 2010 at 3:56 PM, Mark Miller wrote:
>> On 03/05/2010 03:43 PM, Michael McCandless (JIRA) wrote:
>>> [
>>> https://issues.apache.org/jira/browse/LUCENE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:commen
On Fri, Mar 5, 2010 at 3:56 PM, Mark Miller wrote:
> On 03/05/2010 03:43 PM, Michael McCandless (JIRA) wrote:
>> [
>> https://issues.apache.org/jira/browse/LUCENE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842015#action_12842015
>> ]
>>
>>
Yeah, now the patches don't really work on any of the released versions.
Michael McCandless mikemccandless.com> writes:
>
> If Solr/Lucene dev were merged, and queryParser is it's own module,
> this user could simply upgrade his queryParser JAR to get this fix.
>
> Mike
>
-
On 03/05/2010 03:43 PM, Michael McCandless (JIRA) wrote:
[
https://issues.apache.org/jira/browse/LUCENE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842015#action_12842015
]
Michael McCandless commented on LUCENE-2294:
-
[
https://issues.apache.org/jira/browse/LUCENE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-2294:
--
Assignee: Michael McCandless
> Create IndexWriterConfiguration and store all o
[
https://issues.apache.org/jira/browse/LUCENE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842015#action_12842015
]
Michael McCandless commented on LUCENE-2294:
Ha, I see TODO 4.0 comments now.
Op vrijdag 05 maart 2010 18:12:12 schreef Goddard, Michael J.:
> Paul,
>
> It seems like elaborating on my goal would be a good place to start. Our
> users are accustomed to a text engine they've been using for a while, one
> that supports nesting "span queries" arbitrarily deeply with embedded
On Thu, Mar 04, 2010 at 12:23:38PM -0500, Michael McCandless wrote:
> > In a multi-node search cluster, pre-calculating norms at index-time
> > wouldn't work well without additional communication between nodes to
> > gather corpus-wide stats. But I suspect the same trick that works
> > for IDF in
[
https://issues.apache.org/jira/browse/LUCENE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841960#action_12841960
]
Jason Rutherglen commented on LUCENE-2293:
--
{quote}I think we have two options he
[
https://issues.apache.org/jira/browse/LUCENE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841959#action_12841959
]
Uwe Schindler commented on LUCENE-2295:
---
After some discussion with rmuir, we realiz
[
https://issues.apache.org/jira/browse/LUCENE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841942#action_12841942
]
Shai Erera commented on LUCENE-2293:
Thanks Michael. If the int[] are per DW then it's
Paul,
It seems like elaborating on my goal would be a good place to start. Our users
are accustomed to a text engine they've been using for a while, one that
supports nesting "span queries" arbitrarily deeply with embedded wildcard and
range queries, etc. We would like to switch the entire us
[
https://issues.apache.org/jira/browse/LUCENE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841923#action_12841923
]
Michael Busch commented on LUCENE-2293:
---
bq. So about the int[], would that be of th
[
https://issues.apache.org/jira/browse/LUCENE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841915#action_12841915
]
Michael Busch commented on LUCENE-2293:
---
{quote}
This is a great approach for speedi
OK I opened:
https://issues.apache.org/jira/browse/LUCENE-2297
Mike
On Fri, Mar 5, 2010 at 10:25 AM, Michael McCandless
wrote:
> Currently you can't tell IW to use the pool (ie, pool is only enabled
> if you use NRT readers). We should probably make this an option at
> ctor time, for situati
IndexWriter should let you optionally enable reader pooling
---
Key: LUCENE-2297
URL: https://issues.apache.org/jira/browse/LUCENE-2297
Project: Lucene - Java
Issue Type: Improvement
Currently you can't tell IW to use the pool (ie, pool is only enabled
if you use NRT readers). We should probably make this an option at
ctor time, for situations like this. (In fact, in followon
discussions about further improvements to NRT we've already discussed
having such an option to IW's c
[
https://issues.apache.org/jira/browse/LUCENE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reassigned LUCENE-2295:
-
Assignee: Uwe Schindler
> Create a MaxFieldLengthAnalyzer to wrap any other Analyzer and
[
https://issues.apache.org/jira/browse/LUCENE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841877#action_12841877
]
Uwe Schindler edited comment on LUCENE-2295 at 3/5/10 2:25 PM:
-
[
https://issues.apache.org/jira/browse/LUCENE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841877#action_12841877
]
Uwe Schindler commented on LUCENE-2295:
---
In the indexer, the backwards code is hairy
[
https://issues.apache.org/jira/browse/LUCENE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841872#action_12841872
]
Uwe Schindler commented on LUCENE-2295:
---
The TokenFilter is quite easy, only few lin
[
https://issues.apache.org/jira/browse/LUCENE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-2294:
---
Attachment: LUCENE-2294.patch
Patch includes:
* IndexWriterConfig + Test
* Changes to IndexWriter to
[
https://issues.apache.org/jira/browse/LUCENE-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated LUCENE-2296:
--
Attachment: package-summary.png
Here's a similar graph built from Solr sources, to bef
[
https://issues.apache.org/jira/browse/LUCENE-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated LUCENE-2296:
--
Attachment: apiviz.patch
Patch to use the apiviz doclet. This assumes that the apiviz
[
https://issues.apache.org/jira/browse/LUCENE-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated LUCENE-2296:
--
Attachment: package-summary.png
Example class diagram for org.apache.lucene.search. Gr
Include UML diagrams in javadocs
Key: LUCENE-2296
URL: https://issues.apache.org/jira/browse/LUCENE-2296
Project: Lucene - Java
Issue Type: Improvement
Components: Build
Affects Versions: 3.1
[
https://issues.apache.org/jira/browse/LUCENE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841822#action_12841822
]
Shai Erera commented on LUCENE-2295:
This will open the door for more extensible field
[
https://issues.apache.org/jira/browse/LUCENE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841821#action_12841821
]
Shai Erera commented on LUCENE-2293:
Michael - I see that we were on the same page. Pr
Create a MaxFieldLengthAnalyzer to wrap any other Analyzer and provide the same
functionality as MaxFieldLength provided on IndexWriter
---
Key: LUC
[
https://issues.apache.org/jira/browse/LUCENE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841820#action_12841820
]
Shai Erera commented on LUCENE-2294:
Exactly !
Only I hope that if people will intera
[
https://issues.apache.org/jira/browse/LUCENE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841810#action_12841810
]
Michael McCandless commented on LUCENE-2294:
So this will affect these methods
[
https://issues.apache.org/jira/browse/LUCENE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841800#action_12841800
]
Michael McCandless commented on LUCENE-2293:
bq. I think in the future deletes
[
https://issues.apache.org/jira/browse/LUCENE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841745#action_12841745
]
Michael Busch commented on LUCENE-2293:
---
{quote}
Won't this complicate the entire so
[
https://issues.apache.org/jira/browse/LUCENE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841744#action_12841744
]
Michael Busch commented on LUCENE-2293:
---
{quote}
But if each DW maintains its own do
39 matches
Mail list logo
