[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845745#action_12845745
]
Michael Busch commented on LUCENE-2312:
---
The tricky part is to make sure that a read
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845745#action_12845745
]
Michael Busch edited comment on LUCENE-2312 at 3/16/10 6:51 AM:
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845735#action_12845735
]
Jason Rutherglen commented on LUCENE-2312:
--
{quote}This makes the reference to th
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845731#action_12845731
]
Michael Busch commented on LUCENE-2312:
---
{quote}
Do volatile byte arrays work
{quote
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845731#action_12845731
]
Michael Busch edited comment on LUCENE-2312 at 3/16/10 6:12 AM:
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845729#action_12845729
]
Jason Rutherglen commented on LUCENE-2312:
--
{quote}but my goal is it here to impl
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845726#action_12845726
]
Michael Busch commented on LUCENE-2312:
---
{quote}
A quick and easy way to solve this
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845721#action_12845721
]
Jason Rutherglen commented on LUCENE-2312:
--
Just to clarify, I think Mike's refer
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845712#action_12845712
]
Michael Busch commented on LUCENE-2312:
---
{quote} Hmm... what does JMM say about byte
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845703#action_12845703
]
Michael Busch commented on LUCENE-2312:
---
{quote}
Sounds like awesome progress!! Want
[
https://issues.apache.org/jira/browse/LUCENE-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845702#action_12845702
]
Shai Erera commented on LUCENE-2310:
i like the idea of Document to implement Iterable
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845696#action_12845696
]
Jason Rutherglen commented on LUCENE-2312:
--
Payloads works (non-lazy loading), ho
: prime-time as the new solr trunk! Lucene and Solr need to move to a
: common trunk for a host of reasons, including single patches that can
: cover both, shared tags and branches, and shared test code w/o a test
: jar.
Without a clearer picture of how people envision development "overhead"
wor
On Mon, Mar 15, 2010 at 11:41 PM, Mark Miller wrote:
>>
>> Solr moves to Lucene's trunk:
>> /java/trunk, /java/trunk/sol
>
> +1. With the goal of merged dev, merged tests, this looks the best to me.
> Simple to do patches that span both, simple to setup
> Solr to use Lucene trunk rather than jar
On 03/15/2010 11:28 PM, Yonik Seeley wrote:
So, we have a few options on where to put Solr's new trunk:
Solr moves to Lucene's trunk:
/java/trunk, /java/trunk/sol
+1. With the goal of merged dev, merged tests, this looks the best to
me. Simple to do patches that span both, simple to setup
Due to a tremendous amount of work by our newly merged committer
corps, the get-on-lucene-trunk branch (branches/solr) is ready for
prime-time as the new solr trunk! Lucene and Solr need to move to a
common trunk for a host of reasons, including single patches that can
cover both, shared tags and
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845680#action_12845680
]
Jason Rutherglen commented on LUCENE-2312:
--
In thinking about the terms dictionar
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845679#action_12845679
]
Jason Rutherglen commented on LUCENE-2312:
--
Basic term positions working, need to
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845663#action_12845663
]
Jason Rutherglen commented on LUCENE-2312:
--
I have a test case showing the term d
On Mon, Mar 15, 2010 at 05:28:33AM -0500, Michael McCandless wrote:
> I mean specifically one should not have to commit to the precise
> scoring model they will use for a given field, when they index that
> field.
Yeah, I've never seen committing to a precise scoring model at index-time via
Sim ch
[
https://issues.apache.org/jira/browse/LUCENE-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2098:
Attachment: LUCENE-2098.patch
i haven't benchmarked to see if this is any faster, maybe even worse
>
> Personally I'd prefer we just stop adding them, and the current ones work
> their way up like normal if they are so inclined, or the ones that are not
> even around anymore can just stay as they are.
>
This seems reasonable to me.
--
[
https://issues.apache.org/jira/browse/LUCENE-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845530#action_12845530
]
Earwin Burrfoot commented on LUCENE-2320:
-
We could split MergePolicy in two - cla
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845503#action_12845503
]
Jason Rutherglen commented on LUCENE-2312:
--
Also wanted to add that the PostingLi
My 2 cents as one who has no aspirations of ever being a committer.
I think with the pending re-org of contrib and the value of contrib, it
doesn't make much sense to have the distinction between core and contrib
let alone for contributors.
Regarding the former low bar, either prune the list
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845493#action_12845493
]
Jason Rutherglen commented on LUCENE-2312:
--
{quote}Ahh, I think it's because you'
[
https://issues.apache.org/jira/browse/LUCENE-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845490#action_12845490
]
Shai Erera commented on LUCENE-2320:
The thing is that we were at that position alread
[
https://issues.apache.org/jira/browse/LUCENE-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-2325.
Resolution: Fixed
Solr can now run on flex :)
> investigate solr test failures us
[
https://issues.apache.org/jira/browse/LUCENE-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2325:
---
Attachment: LUCENE-2325.patch
The bug was... if you asked for TermsEnum on a non-exi
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845464#action_12845464
]
Michael McCandless commented on LUCENE-2312:
Ahh, I think it's because you're
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845448#action_12845448
]
Jason Rutherglen commented on LUCENE-2312:
--
The code is from FreqProxFieldMergeSt
On Mar 15, 2010, at 1:25 PM, Mark Miller wrote:
> On 03/15/2010 08:33 AM, Grant Ingersoll wrote:
>> Right, Mark. I think we would be effectively raising the bar to some extent
>> for what it takes to be a committer.
>
> That's part of my point though - some are contrib committers with a lower
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845432#action_12845432
]
Michael McCandless commented on LUCENE-2312:
I don't see anything obviously wr
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845428#action_12845428
]
Michael McCandless commented on LUCENE-2324:
{quote}
bq. Seems ilke it's 8 byt
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845426#action_12845426
]
Michael McCandless commented on LUCENE-2324:
bq. Hmm I think we'd need a separ
On 03/15/2010 08:33 AM, Grant Ingersoll wrote:
Right, Mark. I think we would be effectively raising the bar to some extent
for what it takes to be a committer.
That's part of my point though - some are contrib committers with a
lower bar - now they are core/solr committers with that lower ba
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845408#action_12845408
]
Earwin Burrfoot commented on LUCENE-2324:
-
> Seems ilke it's 8 bytes
Object header
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845404#action_12845404
]
Jason Rutherglen commented on LUCENE-2312:
--
Pre-advanced apology for permanently
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845400#action_12845400
]
Michael Busch commented on LUCENE-2324:
---
{quote}
Sounds great - let's test it in pra
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845398#action_12845398
]
Michael Busch edited comment on LUCENE-2324 at 3/15/10 4:34 PM:
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845398#action_12845398
]
Michael Busch commented on LUCENE-2324:
---
{quote}
I think we can do even better, ie,
[
https://issues.apache.org/jira/browse/LUCENE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845391#action_12845391
]
Michael Busch commented on LUCENE-2293:
---
I'll reply on LUCENE-2324.
> IndexWriter h
Welcome guys! :)
Sounds really like some great progress in such a short time!
Michael
On 3/15/10 8:25 AM, Michael McCandless wrote:
The merge of Solr and Lucene dev is well underway... Lucene already
has a bunch of new committers... welcome aboard!
And overnight tons of work was done (and be
[
https://issues.apache.org/jira/browse/LUCENE-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-2311:
--
Assignee: Michael McCandless
> Pass potent SR to IRWarmer.warm(), and also cal
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845374#action_12845374
]
Jason Rutherglen commented on LUCENE-2312:
--
{quote}Good question on skipping - fo
[
https://issues.apache.org/jira/browse/LUCENE-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845370#action_12845370
]
Michael McCandless commented on LUCENE-2320:
bq. Or, maybe, we should think of
The merge of Solr and Lucene dev is well underway... Lucene already
has a bunch of new committers... welcome aboard!
And overnight tons of work was done (and beer, espresso and tea,
depending on your timezone, consumed ;) and now we already
have a branch where Solr has been upgraded to Lucene's tr
[
https://issues.apache.org/jira/browse/LUCENE-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2297:
---
Attachment: LUCENE-2297.patch
Adds IWC.set/getReaderPooling.
> IndexWriter should l
[
https://issues.apache.org/jira/browse/LUCENE-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-2320:
--
Assignee: Michael McCandless
> Add MergePolicy to IndexWriterConfig
>
[
https://issues.apache.org/jira/browse/LUCENE-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845332#action_12845332
]
Michael McCandless commented on LUCENE-2325:
So awesome that we are at the poi
[
https://issues.apache.org/jira/browse/LUCENE-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-2325:
--
Assignee: Michael McCandless
> investigate solr test failures using flex
> ---
Try +contents:term +contents:query. By misplacing the
'+' you're getting the default OR operator and the '+'
is probably being thrown away by the analyzer.
Luke will help here a lot.
HTH
Erick
On Mon, Mar 15, 2010 at 9:46 AM, christian stadler wrote:
> Hi there,
>
> I have an issue with the Qu
[
https://issues.apache.org/jira/browse/LUCENE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-2293.
Resolution: Fixed
> IndexWriter has hard limit on max concurrency
> --
[
https://issues.apache.org/jira/browse/LUCENE-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2325:
Attachment: LUCENE-2325.patch
attached is a very small patch to the Solr branch so it will compile
investigate solr test failures using flex
-
Key: LUCENE-2325
URL: https://issues.apache.org/jira/browse/LUCENE-2325
Project: Lucene - Java
Issue Type: Test
Affects Versions: Flex Branch
Hi there,
I have an issue with the QueryScorer(query) method at the moment and I need
some assistance.
I was indexing my e-book "lucene in action" and based on this index-db I
started to play around with some boolean queries like:
(contents:+term contents:+query)
As a result I'm expecting as a pe
>>> But I don't like baking in search concepts at index time...
>>
> Many scoring models are possible if you store enough stats in the
> index.
>
in general the missing stats seem to fit in two buckets/categories:
1) length normalization pivot: average length in bytes, terms, unique terms
2) term
On Mar 14, 2010, at 6:47 PM, Mark Miller wrote:
>
>
> On 03/14/2010 06:37 PM, Grant Ingersoll wrote:
>> On Mar 14, 2010, at 2:03 PM, Uwe Schindler wrote:
>>
>>
>>> This time a +1 without discuss :-)
>>>
>> Yeah, but Uwe, the thread was DISCUSS, not VOTE! :-)
>>
>
> I had a whole s
On Mar 14, 2010, at 8:25 PM, Yonik Seeley wrote:
> On Sun, Mar 14, 2010 at 5:47 PM, Mark Miller wrote:
>> On 03/14/2010 06:37 PM, Grant Ingersoll wrote:
>>>
>>> On Mar 14, 2010, at 2:03 PM, Uwe Schindler wrote:
>>>
>>>
This time a +1 without discuss :-)
>>>
>>> Yeah, but Uwe
On Mon, Mar 15, 2010 at 12:03 AM, Marvin Humphrey
wrote:
> On Sat, Mar 13, 2010 at 06:41:26AM -0500, Michael McCandless wrote:
>
>> I still don't think similarity should have any bearing during indexing.
>
> Similarity has always, from day one, affected the contents of the index. This
> idea that
[
https://issues.apache.org/jira/browse/LUCENE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845263#action_12845263
]
Michael McCandless commented on LUCENE-2293:
bq. For example, currently a nic
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845261#action_12845261
]
Michael McCandless commented on LUCENE-2324:
Sounds great -- let's test it in
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845257#action_12845257
]
Michael McCandless commented on LUCENE-2312:
{quote}
I got the basics of the t
[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845255#action_12845255
]
Michael McCandless commented on LUCENE-2312:
Yes, commit should flush & sync a
[
https://issues.apache.org/jira/browse/LUCENE-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-2322.
---
Resolution: Fixed
Committed revision: 923112
> Remove verbosity from tests and make configu
65 matches
Mail list logo