On Wed, Apr 27, 2011 at 09:25:14AM -0400, Yonik Seeley wrote:
>...
> But as I said... it seems only fair to meet half way and use the solr
> namespace
> for some modules and the lucene namespace for others.
Please explain this part to me... I really don't understand.
What does "fairness" have to
[
https://issues.apache.org/jira/browse/LUCENE-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026145#comment-13026145
]
Simon Willnauer commented on LUCENE-3023:
-
bq. Attached is the DWPT branch in pat
[
https://issues.apache.org/jira/browse/LUCENE-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026144#comment-13026144
]
Simon Willnauer commented on LUCENE-3023:
-
{quote}
I noticed in the branch the te
On Apr 26, 2011, at 11:12 PM, Chris Male wrote:
> > The two sides/takes seem to be (with some example reasons):
> > 1. pro: for example, modularization can expose features that were
> > traditionally in solr to lucene users.
>
> Some other Pros:
> Easier to test individual pieces. Easier to b
[
https://issues.apache.org/jira/browse/SOLR-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026137#comment-13026137
]
Shinichiro Abe commented on SOLR-2480:
--
Improvement ideas:
1, TikaException is always
Text extraction of password protected files
---
Key: SOLR-2480
URL: https://issues.apache.org/jira/browse/SOLR-2480
Project: Solr
Issue Type: Improvement
Components: contrib - Solr Cell (Tika
[
https://issues.apache.org/jira/browse/LUCENE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026129#comment-13026129
]
Lance Norskog commented on LUCENE-3041:
---
This is an excellent opportunity to redefi
[
https://issues.apache.org/jira/browse/SOLR-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026124#comment-13026124
]
Lance Norskog edited comment on SOLR-2242 at 4/28/11 5:33 AM:
--
[
https://issues.apache.org/jira/browse/SOLR-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026124#comment-13026124
]
Lance Norskog edited comment on SOLR-2242 at 4/28/11 5:33 AM:
--
[
https://issues.apache.org/jira/browse/SOLR-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lance Norskog updated SOLR-2242:
Attachment: SOLR-2242.solr3.1.patch
Putting up or shutting up :)
> Get distinct count of names for
[
https://issues.apache.org/jira/browse/LUCENE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male updated LUCENE-3041:
---
Attachment: LUCENE-3041.patch
Updated patch which removes the stupid test I'd included
> Support Qu
[
https://issues.apache.org/jira/browse/SOLR-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026103#comment-13026103
]
Bill Bell edited comment on SOLR-2242 at 4/28/11 3:51 AM:
--
Lance N
[
https://issues.apache.org/jira/browse/SOLR-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026103#comment-13026103
]
Bill Bell commented on SOLR-2242:
-
Lance Norskog,
What do you want it to be called? I woul
[
https://issues.apache.org/jira/browse/LUCENE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male updated LUCENE-3041:
---
Attachment: LUCENE-3041.patch
A much larger patch that implements full query AST walking.
The probl
[
https://issues.apache.org/jira/browse/SOLR-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-2242:
-
Attachment: SOLR-2242.patch
I noticed that with the original patch applied, SimpleFacetsTest would fail.
Hi Phillipe,
Congrats, I am looking forward to start working with you too ;)
On Tue, Apr 26, 2011 at 8:40 PM, Mark Miller wrote:
> Congrats Phillipe! We are very excited to have you! Your proposal sounds
> great.
>
> - Mark
>
> On Apr 26, 2011, at 8:31 PM, Phillipe Ramalho wrote:
>
> > Hi every
[
https://issues.apache.org/jira/browse/SOLR-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024966#comment-13024966
]
Lance Norskog edited comment on SOLR-2242 at 4/28/11 2:01 AM:
--
[
https://issues.apache.org/jira/browse/LUCENE-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026069#comment-13026069
]
Robert Muir commented on LUCENE-3023:
-
What about TestIndexWriter.testIndexingThenDel
[
https://issues.apache.org/jira/browse/LUCENE-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3023:
Attachment: LUCENE-3023.patch
Attached is the DWPT branch in patch format against trunk (for easie
On Wed, Apr 27, 2011 at 11:49 AM, Michael McCandless
wrote:
> On Wed, Apr 27, 2011 at 9:25 AM, Yonik Seeley
> wrote:
>> On Wed, Apr 27, 2011 at 6:28 AM, Michael McCandless
>> wrote:
>>> Why impose namespace restrictions based on where code was originally
>>> committed? I think the namespace of
[
https://issues.apache.org/jira/browse/LUCENE-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3023:
Attachment: diffMccand.py
ok, i think these issues are resolved. I'm attaching the script Mike wro
Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/7501/
1 tests failed.
REGRESSION: org.apache.solr.client.solrj.TestLBHttpSolrServer.testSimple
Error Message:
expected:<3> but was:<2>
Stack Trace:
junit.framework.AssertionFailedError: expected:<3> but was:<2>
at
[
https://issues.apache.org/jira/browse/LUCENE-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025961#comment-13025961
]
Robert Muir commented on LUCENE-3023:
-
I was helping Simon look at reintegrating this
[
https://issues.apache.org/jira/browse/SOLR-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025958#comment-13025958
]
Stefan Matheis (steffkes) commented on SOLR-2400:
-
Yes =) Ty Uwe, applied t
[
https://issues.apache.org/jira/browse/LUCENE-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Young updated LUCENE-3049:
---
Comment: was deleted
(was: Patch attached.)
> NullPointerException in BiSegGraph.getShortPa
[
https://issues.apache.org/jira/browse/LUCENE-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025929#comment-13025929
]
Jonathan Young edited comment on LUCENE-3049 at 4/27/11 6:17 PM:
--
[
https://issues.apache.org/jira/browse/LUCENE-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Young resolved LUCENE-3049.
Resolution: Duplicate
Lucene Fields: [New] (was: [Patch Available, New])
Recently
[
https://issues.apache.org/jira/browse/LUCENE-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025927#comment-13025927
]
Steven Rowe commented on LUCENE-3049:
-
Jonathan, FYI, you didn't attach a patch?
> N
Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/7488/
1 tests failed.
REGRESSION: org.apache.lucene.collation.TestCollationKeyAnalyzer.testThreadSafe
Error Message:
Java heap space
Stack Trace:
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf
[
https://issues.apache.org/jira/browse/LUCENE-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Young updated LUCENE-3049:
---
Lucene Fields: [New, Patch Available] (was: [New])
Patch attached.
> NullPointerException
NullPointerException in BiSegGraph.getShortPath (in smartcn chinese analyzer)
-
Key: LUCENE-3049
URL: https://issues.apache.org/jira/browse/LUCENE-3049
Project: Lucene - Java
On 27.04.2011 17:40, Amanuel Workneh wrote:
Am I correct that your trial code changes make this version of Lucene.NET
incompatible and un-buildable with any version of .NET prior to 4.0?
As I understand it, 2.9.4g only replaces non-generic collections with
generic ones. Generics was introduced
Sorry, for now, only 4.0.
DIGY
-Original Message-
From: Granroth, Neal V. [mailto:neal.granr...@thermofisher.com]
Sent: Wednesday, April 27, 2011 6:06 PM
To: lucene-net-...@lucene.apache.org
Subject: [Lucene.Net] Lucene.NET 2.9.4g -- only usable with .NET 4.0 ?
Digy,
Am I correct that y
On Wed, Apr 27, 2011 at 9:25 AM, Yonik Seeley
wrote:
> On Wed, Apr 27, 2011 at 6:28 AM, Michael McCandless
> wrote:
>> Why impose namespace restrictions based on where code was originally
>> committed? I think the namespace of refactored code should reflect
>> the nature of the code, not its ori
Digy,
Am I correct that your trial code changes make this version of Lucene.NET
incompatible and un-buildable with any version of .NET prior to 4.0?
- Neal
[
https://issues.apache.org/jira/browse/LUCENE-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-3048.
-
Resolution: Fixed
> Improve BooleanQuery rewrite documentation
> ---
[
https://issues.apache.org/jira/browse/LUCENE-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025819#comment-13025819
]
Simon Willnauer commented on LUCENE-3048:
-
looks useful chris! I will commit it,
[
https://issues.apache.org/jira/browse/LUCENE-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer reassigned LUCENE-3048:
---
Assignee: Simon Willnauer
> Improve BooleanQuery rewrite documentation
> ---
[
https://issues.apache.org/jira/browse/LUCENE-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male updated LUCENE-3048:
---
Attachment: LUCENE-3048.patch
Patch adding comments as mentioned
> Improve BooleanQuery rewrite doc
Improve BooleanQuery rewrite documentation
--
Key: LUCENE-3048
URL: https://issues.apache.org/jira/browse/LUCENE-3048
Project: Lucene - Java
Issue Type: Improvement
Components: Query/Scoring
[
https://issues.apache.org/jira/browse/SOLR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-2272.
Resolution: Fixed
> Join
>
>
> Key: SOLR-2272
> URL: https://is
On 4/27/2011 at 9:25 AM, Yonik wrote:
> it seems only fair to meet half way and use the solr namespace
> for some modules and the lucene namespace for others.
Let's eliminate a source of conflict, and make modules another product that is
neither Lucene nor Solr.
Steve
[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Otto updated SOLR-236:
---
Comment: was deleted
(was: Am I right that trunk is 4.0? What is the newest patch that works on that
c
On Wed, Apr 27, 2011 at 6:28 AM, Michael McCandless
wrote:
> Why impose namespace restrictions based on where code was originally
> committed? I think the namespace of refactored code should reflect
> the nature of the code, not its original origins?
And if it's a very core part of solr that we'
> if its not stated as "this feature is going to Lucene"
It seems as though some people assume that since Lucene is a library, and Solr
is an application, that exposing Solr API *means* making it part of Lucene. It
ain't necessarily so, and it need not be a point of contention.
I want to reite
Fixed the behavior in Revision: 1097097
simon
On Tue, Apr 26, 2011 at 6:14 PM, Shai Erera wrote:
> I think you're right Simon !
>
> Obviously I didn't test it with that scenario in mind :).
>
> Shai
>
> On Tue, Apr 26, 2011 at 6:15 PM, Simon Willnauer
> wrote:
>>
>> hey I wonder how this TEST_
On Wed, Apr 27, 2011 at 8:13 AM, Mark Miller wrote:
> The problem is that Simon says things like, everything should be a module and
> solr should just be sugar on Lucene. That scares Yonik. Then Yonik makes
> comments questioning individual modules. That scares the other guys. Both
> sides ret
Thanks Uwe. I'll work towards the CachingWrapperFilter.
Antony
On 27/04/2011 9:33 PM, Uwe Schindler wrote:
Hi,
In Lucene trunk the Filter gets a ReaderContext which contain a doc base if
available.
For Lucene 2 and 3 this is not available. The Lucene 2.9 code did not change
documented behavi
On Apr 27, 2011, at 12:14 AM, Robert Muir wrote:
> On Tue, Apr 26, 2011 at 11:41 PM, Grant Ingersoll wrote:
>> I think this needs a bit more explanation. AIUI, the primary cause for
>> concern is that by making something a module, you are taking a private,
>> internal API of Solr's and now ma
Phrase (arbitrary delimiter) based autocomplete
---
Key: SOLR-2479
URL: https://issues.apache.org/jira/browse/SOLR-2479
Project: Solr
Issue Type: New Feature
Components: spellchecker
Hi,
In Lucene trunk the Filter gets a ReaderContext which contain a doc base if
available.
For Lucene 2 and 3 this is not available. The Lucene 2.9 code did not change
documented behavior. The fact that Filters always got the top level reader
was never documented (it was just like that in early L
Hi Uwe,
Thanks for the reply.
Things are a bit tangled, because I've used early Solr stuff with DocSet and
have extensively used my own caching Filters because I couldn't get what I
wanted with the standard versions a few years ago. It will take a while to undo
that, but I'm working towards
On Tue, Apr 26, 2011 at 11:41 PM, Grant Ingersoll wrote:
> I think this needs a bit more explanation. AIUI, the primary cause for
> concern is that by making something a module, you are taking a private,
> internal API of Solr's and now making it a public API that must be maintained
> (and ba
On Tue, Apr 26, 2011 at 11:34 PM, Yonik Seeley
wrote:
> On Tue, Apr 26, 2011 at 11:07 PM, Robert Muir wrote:
>> It appears there are some problems with modularization of the code,
>> especially between lucene and solr, so I would like for us to have a
>> discussion on this thread.
>
> The specifi
HyphenationCompoundWordTokenFilter does not work correctly with the german word
Brustamputation
---
Key: LUCENE-3047
URL: https://issues.apache.org/jira/browse/LUCENE-3047
[
https://issues.apache.org/jira/browse/LUCENE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025677#comment-13025677
]
Chris Male commented on LUCENE-3041:
No, you didn't miss something. The RewriteCachi
[
https://issues.apache.org/jira/browse/LUCENE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025669#comment-13025669
]
Simon Willnauer commented on LUCENE-3041:
-
Chris, nice simplification. I have one
[
https://issues.apache.org/jira/browse/LUCENE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Male updated LUCENE-3041:
---
Attachment: LUCENE-3041.patch
Updated patch.
This simplifies the hierarchy a lot. DispatchingQuery
58 matches
Mail list logo
