[
https://issues.apache.org/jira/browse/LUCENE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667175#action_12667175
]
Earwin Burrfoot commented on LUCENE-1524:
-
If you're not using a deterministic tie
[
https://issues.apache.org/jira/browse/LUCENE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luis Alves updated LUCENE-1528:
---
Attachment: lucene_wide_space_v1_src.patch
LUCENE-1528 - Add support for Ideographic Space to the qu
[
https://issues.apache.org/jira/browse/LUCENE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch reassigned LUCENE-1528:
-
Assignee: Michael Busch
> Add support for Ideographic Space to the queryparser - also kn
Moving thread to java-dev...
Uwe Schindler wrote:
You can use the artifact from Hudson as Mike told, but the JAR file
is not
compatible with Lucene 2.4 (because a new SortField constructor for
sorting
against trie encoded fields and the new Superinterface
FieldCache.Parser
leading to Cla
Hi Mike,
That's no problem. O.a.l.search.trie is a new package and depends on new
features in trunk lucene. You can plug in the jar and it works with older
code. The problem here is, that the package trie is compiled against new
lucene 2.9 features like the new SortField constructors. Because of t
Hi Mike, here is why it fails exactly:
If you drop contrib-queries.jar along with lucene-core-2.4.jar into your
application and you try to use the new TrieUtils, it fails because of two
things:
a) The new constructor of SortField(., FieldCache.Parser parser) is not
available in 2.4 -> MethodN
Ahh OK good. I misunderstood, thinking that existing apps (based on
Lucene 2.4) would break if they dropped in the trunk JAR.
Requiring the trunk lucene JAR to play with the trunk trie is
completely fine.
I'll open an issue to strengthen our back-compat tests to do "JAR drop-
in" test.
back-compat tests ("ant test-tag") should test JAR drop-in-ability
--
Key: LUCENE-1529
URL: https://issues.apache.org/jira/browse/LUCENE-1529
Project: Lucene - Java
Issue Type:
[
https://issues.apache.org/jira/browse/LUCENE-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667326#action_12667326
]
Doug Cutting commented on LUCENE-1483:
--
> In principle, the MultiSearcher is obsolete
[
https://issues.apache.org/jira/browse/LUCENE-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667344#action_12667344
]
Uwe Schindler commented on LUCENE-1483:
---
Good comment, you are right! I forget the r
[
https://issues.apache.org/jira/browse/LUCENE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1314:
---
Attachment: LUCENE-1314.patch
OK, new patch. I think it's ready to commit! I'll wa
Support inclusive/exclusive for TrieRangeQuery/-Filter
--
Key: LUCENE-1530
URL: https://issues.apache.org/jira/browse/LUCENE-1530
Project: Lucene - Java
Issue Type: New Feature
Co
[
https://issues.apache.org/jira/browse/LUCENE-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667496#action_12667496
]
Uwe Schindler commented on LUCENE-1507:
---
I like this, it would be good to make memor
[
https://issues.apache.org/jira/browse/LUCENE-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1530:
--
Attachment: LUCENE-1530.patch
The patch. If nobody complains and the removal of not yet releas
[
https://issues.apache.org/jira/browse/LUCENE-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1530:
--
Attachment: LUCENE-1530.patch
Another patch. This maybe a new issue, but it is simplier to do
[
https://issues.apache.org/jira/browse/LUCENE-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667523#action_12667523
]
Yonik Seeley commented on LUCENE-1507:
--
Instead of adding another class, couldn't an
[
https://issues.apache.org/jira/browse/LUCENE-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1530:
--
Summary: Support inclusive/exclusive for TrieRangeQuery/-Filter, remove
default trie variant s
[
https://issues.apache.org/jira/browse/LUCENE-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667524#action_12667524
]
Uwe Schindler commented on LUCENE-1507:
---
Cool idea,
I can do this in TrieRangeQuery
[
https://issues.apache.org/jira/browse/LUCENE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667469#action_12667469
]
Chris Harris commented on LUCENE-1489:
--
As I mentioned on the Solr list, I've discove
[
https://issues.apache.org/jira/browse/LUCENE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667538#action_12667538
]
Michael Busch commented on LUCENE-1528:
---
Looks good, Luis!
I was just wondering if
: > I think, the outdated docs should be removed from the server to also
: > disappear from search engines.
:
: +1
that may be easier said then done.
Each build is done in a clean workspace, and then a config option in
hudson tells it what to copy to the "main" javadoc URL...
http://hudson.zo
[
https://issues.apache.org/jira/browse/LUCENE-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667553#action_12667553
]
Jason Rutherglen commented on LUCENE-1483:
--
{quote}
Uwe: "An improvement of the c
[
https://issues.apache.org/jira/browse/LUCENE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667573#action_12667573
]
Paul Cowan commented on LUCENE-1494:
Hoss, I think you're right. I think the MaskField
[
https://issues.apache.org/jira/browse/LUCENE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667573#action_12667573
]
pcowan edited comment on LUCENE-1494 at 1/26/09 7:16 PM:
-
Hoss
Chris Hostetter wrote:
: > I think, the outdated docs should be removed from the server to also
: > disappear from search engines.
We do not want unofficial builds to be indexed by search engines anyway.
Folks who're searching for information about Lucene should not be
referred to unreleased
Doug Cutting wrote:
We should add a robots.txt for Hudson that prohibits crawling, no?
At my request, Nigel just added one.
Doug
-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail
26 matches
Mail list logo
