Ohh, right. I missed that. Indeed after I call nextPosition again, it prints
1. Thanks !
Shai
On Thu, Aug 27, 2009 at 7:09 AM, Michael Busch wrote:
> The first occurrence of your term does not have a payload, the second one
> does. So getPayloadLength() correctly returns 0, because the TermPosi
The first occurrence of your term does not have a payload, the second
one does. So getPayloadLength() correctly returns 0, because the
TermPositions is at the first occurrence. If you call nextPosition()
again and then dump the payload length it should be 1.
Michael
On 8/26/09 8:51 PM, Shai
Hi
I don't know if it's supported or not, but I wrote the following simple
example code to describe what I want.
Directory dir = new RAMDirectory();
Analyzer a = new SimpleAnalyzer();
IndexWriter writer = new IndexWriter(dir, a, MaxFieldLength.UNLIMITED);
Document doc = new Docume
Mark Miller wrote:
> I'm tempted to say lets start the freeze tomorrow instead - I could do
> another full day of doc/packaging no problem I think (a bunch left to do
> on the website stuff alone) - and technically the releaseToDo wants
> everything to go through a patch in JIRA first while in free
[
https://issues.apache.org/jira/browse/LUCENE-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748213#action_12748213
]
Michael McCandless commented on LUCENE-1860:
bq. should we keep the good old R
[
https://issues.apache.org/jira/browse/LUCENE-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch resolved LUCENE-1851.
---
Resolution: Fixed
Fixed it. Sorry about that.
Committed revision 808224.
> 'ant javacc' in
[
https://issues.apache.org/jira/browse/LUCENE-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748157#action_12748157
]
Uwe Schindler commented on LUCENE-1860:
---
If we change this, should we keep the good
[
https://issues.apache.org/jira/browse/LUCENE-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adriano Crestani updated LUCENE-950:
Attachment: lucene_950_08_26_2009.patch
This patch fixes the bug, it no longer throws Illeg
[
https://issues.apache.org/jira/browse/LUCENE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748127#action_12748127
]
Simon Willnauer commented on LUCENE-1817:
-
Robert, I commited the javadoc changes.
[
https://issues.apache.org/jira/browse/LUCENE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748126#action_12748126
]
Robert Muir commented on LUCENE-1817:
-
i looked at this file format and I am going to
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748122#action_12748122
]
Tim Smith commented on LUCENE-1859:
---
On documentation:
any warnings/precautions should a
[
https://issues.apache.org/jira/browse/LUCENE-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1861:
Component/s: Build
> Add contrib libs to classpath for javadoc
> -
Add contrib libs to classpath for javadoc
-
Key: LUCENE-1861
URL: https://issues.apache.org/jira/browse/LUCENE-1861
Project: Lucene - Java
Issue Type: Wish
Reporter: Mark Miller
[
https://issues.apache.org/jira/browse/LUCENE-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1860:
---
Attachment: LUCENE-1860.patch
> switch MultiTermQuery to "constant score auto" rewri
[
https://issues.apache.org/jira/browse/LUCENE-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1860:
---
Component/s: Search
Priority: Minor (was: Major)
> switch MultiTermQuery to
switch MultiTermQuery to "constant score auto" rewrite by default
-
Key: LUCENE-1860
URL: https://issues.apache.org/jira/browse/LUCENE-1860
Project: Lucene - Java
Issue Type: Im
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748109#action_12748109
]
Marvin Humphrey commented on LUCENE-1859:
-
> I don't believe there is ever any val
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748103#action_12748103
]
Tim Smith commented on LUCENE-1859:
---
bq. Death by a thousand cuts. This is one cut.
by
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748102#action_12748102
]
Marvin Humphrey commented on LUCENE-1859:
-
> i fail to see the complexity of addin
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748091#action_12748091
]
Tim Smith edited comment on LUCENE-1859 at 8/26/09 12:18 PM:
-
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748091#action_12748091
]
Tim Smith commented on LUCENE-1859:
---
i fail to see the complexity of adding one method t
[
https://issues.apache.org/jira/browse/LUCENE-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adriano Crestani updated LUCENE-1823:
-
Attachment: lucene_1823_foo_bug_08_26_2009.patch
{quote}
We can also implement:
* f
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748089#action_12748089
]
Marvin Humphrey commented on LUCENE-1859:
-
IMO, the benefit of adding these theore
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748083#action_12748083
]
Robert Muir commented on LUCENE-1859:
-
bq. perhaps it should be the responsibility of
Agreed. I'll open an issue...
Mike
On Wed, Aug 26, 2009 at 10:26 AM, Mark Miller wrote:
> Why wouldn't we? Isn't it just as much of a break to have the QP start
> spitting them off? Except now its confusing because you get something
> different by default from the QP and by default from the dire
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748082#action_12748082
]
Tim Smith commented on LUCENE-1859:
---
bq. which non-intelligent tokenizers are you referr
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748079#action_12748079
]
Robert Muir commented on LUCENE-1859:
-
bq. If someone feeds a large text document with
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748077#action_12748077
]
Tim Smith commented on LUCENE-1859:
---
bq. I would set this to minor and would not take ca
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1859:
--
Priority: Minor (was: Major)
> TermAttributeImpl's buffer will never "shrink" if it grows too
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748072#action_12748072
]
Uwe Schindler commented on LUCENE-1859:
---
The problem is, that it may be possible to
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748071#action_12748071
]
Tim Smith edited comment on LUCENE-1859 at 8/26/09 11:31 AM:
-
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748071#action_12748071
]
Tim Smith commented on LUCENE-1859:
---
b1. The worst-case scenario seems kind of theoretic
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748064#action_12748064
]
Marvin Humphrey commented on LUCENE-1859:
-
The worst-case scenario seems kind of t
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748046#action_12748046
]
Mark Harwood commented on LUCENE-1486:
--
It does not stand on it's own as it is merely
[
https://issues.apache.org/jira/browse/LUCENE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1817:
Attachment: dataFiles.zip
the two files in this directory need to be placed in smartcn/test under
[
https://issues.apache.org/jira/browse/LUCENE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748025#action_12748025
]
Robert Muir edited comment on LUCENE-1817 at 8/26/09 10:21 AM:
-
[
https://issues.apache.org/jira/browse/LUCENE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1817:
Attachment: LUCENE-1817.patch
patch adds:
* load custom dictionaries when the analyzer has been co
[
https://issues.apache.org/jira/browse/LUCENE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748025#action_12748025
]
Robert Muir commented on LUCENE-1817:
-
to make matters more complex, trying to load a
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747982#action_12747982
]
Grant Ingersoll commented on LUCENE-1486:
-
I'm not sure why the ComplexPhraseQuery
On Wed, Aug 26, 2009 at 4:49 PM, Mark Miller wrote:
> Simon Willnauer wrote:
>> I just talked to Robert about refactoring of smartcn for the next
>> releases > 2.9. Robert raised a question if we should mark smartcn as
>> experimental so that we can change interfaces and public methods etc.
>> duri
[
https://issues.apache.org/jira/browse/LUCENE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-1817:
Attachment: LUCENE-1817-mark-cn-experimental.patch
We should mark the smartcn module expe
[
https://issues.apache.org/jira/browse/LUCENE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747967#action_12747967
]
Robert Muir commented on LUCENE-1817:
-
Uwe, i agree. currently it does do the autodete
[
https://issues.apache.org/jira/browse/LUCENE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747966#action_12747966
]
Uwe Schindler commented on LUCENE-1817:
---
In my opinion, the loader should be able to
[
https://issues.apache.org/jira/browse/LUCENE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747963#action_12747963
]
Robert Muir commented on LUCENE-1817:
-
I am looking at this today. One thing about thi
Simon Willnauer wrote:
> I just talked to Robert about refactoring of smartcn for the next
> releases > 2.9. Robert raised a question if we should mark smartcn as
> experimental so that we can change interfaces and public methods etc.
> during the refactoring. Would that make sense for 2.9 or is th
I just talked to Robert about refactoring of smartcn for the next
releases > 2.9. Robert raised a question if we should mark smartcn as
experimental so that we can change interfaces and public methods etc.
during the refactoring. Would that make sense for 2.9 or is there no
such thing as a back com
[
https://issues.apache.org/jira/browse/LUCENE-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747961#action_12747961
]
Luis Alves commented on LUCENE-1851:
{code}
javacc:
[javacc] Java Compiler Compiler
Why wouldn't we? Isn't it just as much of a break to have the QP start
spitting them off? Except now its confusing because you get something
different by default from the QP and by default from the direct object -
sometimes this could make sense, I don't think the QP has to be locked
into Query obj
[
https://issues.apache.org/jira/browse/LUCENE-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Smith resolved LUCENE-1842.
---
Resolution: Won't Fix
I'm happy with just having the Tokenizer's provide the AttributeSource in the
I wish JIRA wouldn't default to major - it would make those tags much
more useful.
Simon Willnauer (JIRA) wrote:
> [
> https://issues.apache.org/jira/browse/LUCENE-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Simon Willnauer updated LUCENE-1815:
> -
[
https://issues.apache.org/jira/browse/LUCENE-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-1815:
Priority: Minor (was: Major)
I don't think this shouldn't be major!
> Geohash encode/dec
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747943#action_12747943
]
Tim Smith commented on LUCENE-1859:
---
it seems like the new TokenStream API may aggravate
[
https://issues.apache.org/jira/browse/LUCENE-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747942#action_12747942
]
Uwe Schindler commented on LUCENE-1859:
---
This also applies to Token. If we fix that,
thx mike!
simon
On Wed, Aug 26, 2009 at 2:35 PM, wrote:
> Author: mikemccand
> Date: Wed Aug 26 12:35:59 2009
> New Revision: 807982
>
> URL: http://svn.apache.org/viewvc?rev=807982&view=rev
> Log:
> LUCENE-1845: rollback changes to build.xml's
>
> Modified:
> lucene/java/trunk/build.xml
>
TermAttributeImpl's buffer will never "shrink" if it grows too big
--
Key: LUCENE-1859
URL: https://issues.apache.org/jira/browse/LUCENE-1859
Project: Lucene - Java
Issue Type:
publish-maven is run on my cron script on the Hudson zone, where it
copies the maven artifacts off of the Lucene Zone and onto the Hudson
Zone.
FWIW, committers can get Hudson accounts. See http://wiki.apache.org/general/Hudson
. Committers can also get Lucene Zone access to, if it is need
[
https://issues.apache.org/jira/browse/LUCENE-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Elschot reopened LUCENE-1851:
--
Reopening only to make sure my last comment is not missed before the impending
2.9 release.
> 'a
I think pub-maven is still used, but let me check.
On Aug 26, 2009, at 8:47 AM, Michael McCandless wrote:
Thanks Grant.
Should we remove https://svn.apache.org/repos/asf/lucene/java/nightly
entirely? Ie we are not using any of these files anymore?:
README.txt nightly.properties ni
Thanks Grant.
Should we remove https://svn.apache.org/repos/asf/lucene/java/nightly
entirely? Ie we are not using any of these files anymore?:
README.txt nightly.properties nightly.sh.bak publish-maven.sh
nightly.cronnightly.sh
Mike
On Wed, Aug 26, 2009 at 8:20 AM, G
I'm tempted to say lets start the freeze tomorrow instead - I could do
another full day of doc/packaging no problem I think (a bunch left to do
on the website stuff alone) - and technically the releaseToDo wants
everything to go through a patch in JIRA first while in freeze (not a
bad idea at all)
So it is possible by editing this script to pass additional options with -D
to some of the ANT commands.
Thanks for the insight, that also helps me very much with the clover update.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Ori
+1
Mike
On Wed, Aug 26, 2009 at 8:20 AM, Grant Ingersoll wrote:
> +1
>
> On Aug 25, 2009, at 10:11 PM, Mark Miller wrote:
>
>> This are very old and not very useful anymore. Should we pull this page?
>> Its kind of an embarrassment if we don't actually maintain it to be
>> remotely current. These
[
https://issues.apache.org/jira/browse/LUCENE-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1845:
---
Fix Version/s: (was: 2.9)
3.0
Moving to 3.0... this need not
[
https://issues.apache.org/jira/browse/LUCENE-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747913#action_12747913
]
Michael McCandless commented on LUCENE-1845:
OK I think we should simply rever
+1
On Aug 25, 2009, at 10:11 PM, Mark Miller wrote:
This are very old and not very useful anymore. Should we pull this
page?
Its kind of an embarrassment if we don't actually maintain it to be
remotely current. These all with Lucene 1.2, 1.3 ...
--
- Mark
http://www.lucidimagination.com
Here's what is currently run on Hudson as shell:
set -x
export FORREST_HOME=/export/home/nigel/tools/forrest/latest
ANT_HOME=/export/home/hudson/tools/ant/latest
ARTIFACTS=$WORKSPACE/artifacts
MAVEN_ARTIFACTS=$WORKSPACE/maven_artifacts
TRUNK=$WORKSPACE/trunk
mkdir -p $ARTIFACTS
mkdir -p $MAVEN
[
https://issues.apache.org/jira/browse/LUCENE-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747884#action_12747884
]
Paul Elschot commented on LUCENE-1851:
--
After svn update I still have the output belo
Right, it is confusing!
QueryParser has already cutover to auto constant score, by default.
But for direct instantiation of one of the MultiTermQueries, we still
default to scoring BooleanQuery, but have declared that in 3.0 this
will also switch to auto constant score. I'm tempted to simply swi
hmm...I guess this javadoc from MultiTermQuery confused me:
* Note that {...@link QueryParser} produces
* MultiTermQueries using {...@link
* #CONSTANT_SCORE_AUTO_REWRITE_DEFAULT} by default.
Uwe Schindler wrote:
> Even the old RangeQuery does it. Only the new class TermRangeQuery uses
> const
[
https://issues.apache.org/jira/browse/LUCENE-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747874#action_12747874
]
Shai Erera commented on LUCENE-1849:
Yes I know that - I remember that you once ran w/
Even the old RangeQuery does it. Only the new class TermRangeQuery uses
constant score (and the also deprecated ConstantScoreRangeQuery).
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Michael McCandless
Unfortunately, Prefix/Wildcard/FuzzyQuery, etc., still rewrite to scoring
BooleanQuery by default, for now. In 3.0 this will change to constant
score auto mode. At least, that's the plan now... however,
QueryParser will produce queries in constant score auto mode, so we
could consider changing th
:)
there we go!
On Wed, Aug 26, 2009 at 11:24 AM, Michael
McCandless wrote:
> Yay!
>
> Mike
>
> On Wed, Aug 26, 2009 at 1:24 AM, Apache Hudson
> Server wrote:
>> See http://hudson.zones.apache.org/hudson/job/Lucene-trunk/929/changes
>>
>>
>>
>>
Yay!
Mike
On Wed, Aug 26, 2009 at 1:24 AM, Apache Hudson
Server wrote:
> See http://hudson.zones.apache.org/hudson/job/Lucene-trunk/929/changes
>
>
>
> -
> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
> For addi
[
https://issues.apache.org/jira/browse/LUCENE-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747851#action_12747851
]
Michael McCandless commented on LUCENE-1849:
We do need to index your memory c
[
https://issues.apache.org/jira/browse/LUCENE-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747836#action_12747836
]
Simon Willnauer commented on LUCENE-1845:
-
I added the short discussion I had on l
I would suggest we move it to the wiki (I think we can simply remove
the 1.2 and 1.3 benchmarks) and try to get a more recent benchmark
soon. In other words a benchmark page on the wiki could be maintained
by all users and commiters and would encurage people to publish their
results as the hurdle i
[
https://issues.apache.org/jira/browse/LUCENE-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747805#action_12747805
]
Shai Erera commented on LUCENE-1849:
bq. I think somewhere in LUCENE-1483 is the answe
78 matches
Mail list logo
