On Tue, Mar 29, 2011 at 8:09 PM, Chris Hostetter
wrote:
>
> These messages are now logged on every request, even if no transformer or
> globs are used in the fl.
>
> seems like this should be a DEBUG message at best?
Yep, I had added that to my patch as debugging only (and I thought I
had added a
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012823#comment-13012823
]
Robert Muir commented on SOLR-2338:
---
I see, as far as using NamedList for the new Similar
[
https://issues.apache.org/jira/browse/SOLR-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi resolved SOLR-2445.
--
Resolution: Fixed
trunk: Committed revision 1086821.
3x: Committed revision 1086822.
> unknown
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012812#comment-13012812
]
Robert Muir commented on SOLR-2338:
---
By the way on the last part, its probably hard to se
This vote has passed. I will do the necessary publishing steps tomorrow AM
(EDT).
Thanks to everyone who helped!
-Grant
On Mar 29, 2011, at 3:38 PM, Simon Willnauer wrote:
> +1
>
> I ran the tests & checked signatures. Looks good to me.
>
>
> On Tue, Mar 29, 2011 at 9:27 PM, Dawid Weiss
>
It's def. not 1.4.2. If anything it would be 1.5. The point is here people
shouldn't go wondering where all the other releases are.
On Mar 29, 2011, at 9:30 PM, Upayavira wrote:
>> -version. Solr 3.1 is the next release after Solr 1.4.1.
>> +version. Solr 3.1 contains Lucene 3.1 and is the
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012809#comment-13012809
]
Robert Muir commented on SOLR-2338:
---
{quote}
i don't personally think it would be confusi
[
https://issues.apache.org/jira/browse/LUCENE-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012810#comment-13012810
]
Chris Male commented on LUCENE-3003:
+1 to committing this change then tackling the i
> -version. Solr 3.1 is the next release after Solr 1.4.1.
> +version. Solr 3.1 contains Lucene 3.1 and is the release after Solr
is the next *minor* release after Solr 1.4.1.
(or, you could say "Solr 3.1 contains Lucene 3.1, and is the release
that would otherwise have been Solr 1.4.2").
Upay
[
https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012806#comment-13012806
]
Upayavira commented on SOLR-2399:
-
I've updated my github repo with an implementation of th
[
https://issues.apache.org/jira/browse/SOLR-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012805#comment-13012805
]
Koji Sekiguchi commented on SOLR-2445:
--
I missed Wiki, but I only looked how initHandl
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012802#comment-13012802
]
Hoss Man commented on SOLR-2338:
bq. but if you think its not confusing, we could support t
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012792#comment-13012792
]
Robert Muir commented on SOLR-2338:
---
Hoss, thanks for looking at the patch.
As far as th
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012787#comment-13012787
]
Hoss Man edited comment on SOLR-2338 at 3/30/11 12:37 AM:
--
skimmin
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012787#comment-13012787
]
Hoss Man commented on SOLR-2338:
skimming the patch, the one thing i'm not clear on is what
I think taking them out is ok
or log.fine
On Tue, Mar 29, 2011 at 8:09 PM, Chris Hostetter
wrote:
>
>
> These messages are now logged on every request, even if no transformer or
> globs are used in the fl.
>
> seems like this should be a DEBUG message at best?
>
> if folks really think it's imp
These messages are now logged on every request, even if no transformer or
globs are used in the fl.
seems like this should be a DEBUG message at best?
if folks really think it's important to log this on every request, then
shouldn't these three key=val pairs just be factored into the main req
[
https://issues.apache.org/jira/browse/LUCENE-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012775#comment-13012775
]
Robert Muir commented on LUCENE-3000:
-
bq. i also seem to recall that most projects p
[
https://issues.apache.org/jira/browse/SOLR-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-2435:
---
Fix Version/s: (was: 3.1)
3.2
no one seems to think this is a 3.1 blocker, moving to 3.
[
https://issues.apache.org/jira/browse/LUCENE-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012771#comment-13012771
]
Hoss Man commented on LUCENE-3000:
--
i also seem to recall that most projects put the "ap
: Hi, this is my first post to the mailing list. I'm working on a commercial
Welcome!
: My DTD works for our internal version of queryElevation.xml, but since the
: ATTRIB name of the tag could be anything, I'm not sure how to write a
: DTD that would validate any valid query elevation file.
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012737#comment-13012737
]
Uwe Schindler commented on LUCENE-3001:
---
bq. The default precisionStep should not h
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012727#comment-13012727
]
Ryan McKinley commented on LUCENE-3001:
---
The default precisionStep should not have
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012725#comment-13012725
]
Uwe Schindler commented on LUCENE-3001:
---
Just to add: Solr can handle this, too: If
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012723#comment-13012723
]
Uwe Schindler commented on LUCENE-3001:
---
bq. EG we can record that "this field is a
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012705#comment-13012705
]
Uwe Schindler commented on LUCENE-3001:
---
bq. I don't see why Solr needs to match Lu
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012694#comment-13012694
]
Yonik Seeley commented on LUCENE-3001:
--
bq. The default precisionStep should not be
[
https://issues.apache.org/jira/browse/SOLR-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012690#comment-13012690
]
Ryan McKinley commented on SOLR-2433:
-
Any objects to this?
The objection to SOLR-332
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012689#comment-13012689
]
Michael McCandless commented on LUCENE-3001:
With stored fields we are free t
[
https://issues.apache.org/jira/browse/LUCENE-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012687#comment-13012687
]
Jason Rutherglen commented on LUCENE-3003:
--
bq. Ie Pulsing is good for terms tha
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012680#comment-13012680
]
Uwe Schindler commented on LUCENE-3001:
---
The problem with the binary encoding in Lu
[
https://issues.apache.org/jira/browse/LUCENE-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012683#comment-13012683
]
Michael McCandless commented on LUCENE-3003:
bq. I'd guess that pulsing shoul
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012671#comment-13012671
]
Yonik Seeley commented on LUCENE-3001:
--
I'd like to keep Solr's binary encoding.
Per
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012667#comment-13012667
]
Ryan McKinley commented on LUCENE-3001:
---
I backed this out of lucene for now.
It w
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012660#comment-13012660
]
Robert Muir commented on LUCENE-3001:
-
bq. The solr support for numeric fields writes
[
https://issues.apache.org/jira/browse/LUCENE-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012659#comment-13012659
]
Jason Rutherglen commented on LUCENE-3003:
--
{quote}Eventually we should fold thi
[
https://issues.apache.org/jira/browse/LUCENE-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3003:
---
Attachment: LUCENE-3003.patch
Attached patch. I moved most of UnInvertedField into
[
https://issues.apache.org/jira/browse/SOLR-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-2433:
Attachment: SOLR-2433-ProtectedFieldProperties.patch
this patch makes the constances protected and a
Move UnInvertedField into Lucene core
-
Key: LUCENE-3003
URL: https://issues.apache.org/jira/browse/LUCENE-3003
Project: Lucene - Java
Issue Type: Improvement
Components: Index
Report
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012644#comment-13012644
]
Uwe Schindler commented on LUCENE-3001:
---
Hi, sorry I saw the commit but this is not
> : As is, Transformers do not have access to SolrParams -- i think that
> : is OK, but we should discuss
> :
> : TransformerFactory could easily be changed to take SolrParams or
> : SolrQueryRequest.
>
> independent of whatever details get hashed out on the syntax to make it
> easy to specify sim
We already have a release for .NET 2.0 (Lucene.Net 2.9.2). So, jumping to
4.0 shouldn't be a problem for Lucene,Net community.
DIGY
On Tue, Mar 29, 2011 at 10:31 PM, Troy Howard wrote:
> Sounds good to me. I have done this previously in a local branch and
> noticed massive performance improvem
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012642#comment-13012642
]
Hoss Man commented on SOLR-2444:
bq. I'd like to make sure we have a simple way to configur
+1
I ran the tests & checked signatures. Looks good to me.
On Tue, Mar 29, 2011 at 9:27 PM, Dawid Weiss
wrote:
> +1
>
> Checked the clustering stuff again, works fine.
>
> Dawid
>
> On Tue, Mar 29, 2011 at 8:30 PM, Chris Hostetter
> wrote:
>>
>> : Artifacts are at http://people.apache.org/~gsi
Sounds good to me. I have done this previously in a local branch and
noticed massive performance improvements. Removing all the casting in
the library makes for dramatic speedups.
As a side note: Chris Currens is in the process of benchmarking
Lucene.Net running under .NET 4.0 vs 3.5 vs 2.0... Thi
+1
Checked the clustering stuff again, works fine.
Dawid
On Tue, Mar 29, 2011 at 8:30 PM, Chris Hostetter
wrote:
>
> : Artifacts are at http://people.apache.org/~gsingers/staging_area/rc3/.
> : Please vote as you see appropriate. Vote closes on March 29th.
>
> +1
>
> -Hoss
>
>
Add tests.iter.min to improve controlling tests.iter's behavior
---
Key: LUCENE-3002
URL: https://issues.apache.org/jira/browse/LUCENE-3002
Project: Lucene - Java
Issue Type: Test
After this directory layout changes; what about replacing ArrayLists,
Hashtables etc, with appropriate Generics? This would bring us very close
to lucene 3.0.3 (and not hard to do with the help of VS).
DIGY
On Tue, Mar 29, 2011 at 10:02 PM, Troy Howard wrote:
> Sounds good. I'll make a tag pri
could you give a shout to the list when that gets stabilized?
On Tue, Mar 29, 2011 at 3:02 PM, Troy Howard wrote:
> Sounds good. I'll make a tag prior to starting the directory changes,
> but I'll commit changes to trunk.
>
> Thanks,
> Troy
>
>
> On Tue, Mar 29, 2011 at 11:55 AM, digy digy wrot
Thanks Hoss. This is a good idea. I'll open an issue to track this.
Shai
On Tue, Mar 29, 2011 at 7:11 PM, Chris Hostetter
wrote:
> : I see. On the other hand, it's a bit annoying when you run with X=100 for
> : the purpose of catching a multi-threaded bug, which occurs after the 2nd
> : iteratio
Sounds good. I'll make a tag prior to starting the directory changes,
but I'll commit changes to trunk.
Thanks,
Troy
On Tue, Mar 29, 2011 at 11:55 AM, digy digy wrote:
> +1. No pending commits.
> A copy of the current trunk somewhere else(tag, branches etc.) would be good
> too.
>
> DIGY.
>
>
+1. No pending commits.
A copy of the current trunk somewhere else(tag, branches etc.) would be good
too.
DIGY.
On Tue, Mar 29, 2011 at 9:38 PM, Troy Howard wrote:
> Looks like we have a 'lazy consensus', in that, no one has raised any
> significant objections, a few minor modifications have
[
https://issues.apache.org/jira/browse/LUCENE-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012609#comment-13012609
]
Grant Ingersoll commented on LUCENE-2995:
-
bq. if that's in the scope for what yo
Looks like we have a 'lazy consensus', in that, no one has raised any
significant objections, a few minor modifications have been suggested
(which sound totally reasonable), and those who did vote were
positive.
Barring any objections, this vote passes.
Since DIGY and Scott seem to have gotten th
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012606#comment-13012606
]
Ryan McKinley commented on SOLR-2444:
-
This makes sense -- i can see letting a componen
: Artifacts are at http://people.apache.org/~gsingers/staging_area/rc3/.
: Please vote as you see appropriate. Vote closes on March 29th.
+1
-Hoss
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional co
[
https://issues.apache.org/jira/browse/LUCENE-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012600#comment-13012600
]
Michael McCandless commented on LUCENE-2995:
How about just "suggest"?
I don
I tweaked them a bit :)
Mike
http://blog.mikemccandless.com
On Tue, Mar 29, 2011 at 2:12 PM, Grant Ingersoll wrote:
> I hate editing by email. Having said that, I believe I've incorporated
> everyone's comments.
> The announcements are in SVN
> at https://svn.apache.org/repos/asf/lucene/dev/mi
[
https://issues.apache.org/jira/browse/LUCENE-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012596#comment-13012596
]
Steven Rowe commented on LUCENE-2995:
-
Or maybe "did-you-mean" or "instead"?
> facto
dooh -- sorry did not run ant clean first!
fix to follow
On Tue, Mar 29, 2011 at 2:04 PM, Apache Hudson Server
wrote:
> Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6508/
>
> 102 tests failed.
> REGRESSION: org.apache.solr.BasicFunctionalityTest.testIgnoredFields
>
I hate editing by email. Having said that, I believe I've incorporated
everyone's comments.
The announcements are in SVN at
https://svn.apache.org/repos/asf/lucene/dev/misc/announcements
Please submit patches or edit as you see fit if you have a commit bit.
-Grant
On Mar 27, 2011, at 8:54 P
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012582#comment-13012582
]
Hoss Man commented on SOLR-2444:
bq. I think it makes sense because it is the place you sel
+1
Ran the tests and the example/tutorial for Solr. All is well and looks good.
Erik
On Mar 26, 2011, at 22:07 , Grant Ingersoll wrote:
> Artifacts are at http://people.apache.org/~gsingers/staging_area/rc3/.
> Please vote as you see appropriate. Vote closes on March 29th.
>
> I'v
[
https://issues.apache.org/jira/browse/LUCENE-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012577#comment-13012577
]
Steven Rowe commented on LUCENE-2995:
-
bq. maybe "query-suggester" or "term-suggester
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012574#comment-13012574
]
Ryan McKinley commented on LUCENE-3001:
---
Added to trunk in #1086651
I'll wait for
[
https://issues.apache.org/jira/browse/SOLR-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012575#comment-13012575
]
Hoss Man commented on SOLR-2445:
that's a fairly old static, probably from before we even s
[
https://issues.apache.org/jira/browse/LUCENE-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012569#comment-13012569
]
Hoss Man commented on LUCENE-2995:
--
i don't really have any better suggestions (ack, i h
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012566#comment-13012566
]
Ryan McKinley commented on LUCENE-3001:
---
This is trivial now that lucene+solr share
: As is, it is not defined by a param, but via solrconfig:
:
:
: nl
:
:
: As is, Transformers do not have access to SolrParams -- i think that
: is OK, but we should discuss
:
: TransformerFactory could easily be changed to take SolrParams or
: SolrQueryRequest.
independent of whatever deta
: I see. On the other hand, it's a bit annoying when you run with X=100 for
: the purpose of catching a multi-threaded bug, which occurs after the 2nd
: iteration ...
:
: I can propose another parameter, tests.iter.break.on.failure, but it's too
: much I guess :).
suggestion: add two params...
[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated LUCENE-3001:
--
Attachment: LUCENE-3001-TrieFieldHelper.patch
This patch moves logic from TrieField to a helpe
Add TrieFieldHelper lucene so we can write solr compatible Trie* fields w/o
solr dependency
---
Key: LUCENE-3001
URL: https://issues.apache.org/jira/browse/LUCENE-3001
[
https://issues.apache.org/jira/browse/SOLR-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved SOLR-2396.
---
Resolution: Fixed
Committed revision 1086637.
> add [ICU]CollationField
> ---
>
>
[
https://issues.apache.org/jira/browse/SOLR-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012548#comment-13012548
]
Rama Roberts commented on SOLR-1855:
Thanks- this is helpful.
You should add to the as
+1 to release.
I verified sigs on the src tgz packages, verified that "ant test" passes
for each, ran Lucene's demo Index/SearchFiles, spot checked a few things.
Nice work everyone! First release after the merger is quite a
doozie...
Mike
http://blog.mikemccandless.com
On Tue, Mar 29, 2011 at
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir reassigned SOLR-2338:
-
Assignee: Robert Muir
> improved per-field similarity integration into schema.xml
> --
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012538#comment-13012538
]
Robert Muir commented on SOLR-2338:
---
I'll commit this in a few days unless anyone objects
Lucene release artifacts should be named apache-lucene-*
Key: LUCENE-3000
URL: https://issues.apache.org/jira/browse/LUCENE-3000
Project: Lucene - Java
Issue Type: Bug
Affects Vers
[
https://issues.apache.org/jira/browse/LUCENE-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012524#comment-13012524
]
Grant Ingersoll commented on LUCENE-2995:
-
yeah, I like suggestions or suggester
Modules need release packaging
--
Key: LUCENE-2999
URL: https://issues.apache.org/jira/browse/LUCENE-2999
Project: Lucene - Java
Issue Type: Bug
Affects Versions: 4.0
Reporter: Grant Ingersoll
[
https://issues.apache.org/jira/browse/LUCENE-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-2998.
-
Resolution: Fixed
> Forward Port 3.1 Ant release tasks
> ---
OK the failure is because of the interaction of CMS and LogMP.
I think we should just cut this test back to SMS, since it's
specifically testing the invariants of LogMP in a "controlled"
setting. I'll commit that...
The problem happens because a BG merge finishes before (in time) the
merges befo
I'd prefer plain field names, even for "pseudo fields", in same way as "score".
Then do the config of what a pseudo field means outside of fl=
Example concept:
&fl=title,explain
&transformer.explain.field=explain
&f.explain.transformer.explain.type=text
&fl=title,myhltitle
&f.title.transformer.h
On Tue, Mar 29, 2011 at 10:44 AM, Ryan McKinley wrote:
> more complex details would be handled via standard parameters -- for
> highlighting, we would use the existing parameters to setup the
> highlighter.
>
> fl=id,[hl:title],[hl:body]&hl.fragsize=100
>
> We could even use the standard per-field
[
https://issues.apache.org/jira/browse/LUCENE-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-2573:
Attachment: LUCENE-2573.patch
next iterations.
* added JavaDoc to all classes and interfac
On Tue, Mar 29, 2011 at 10:30 AM, Yonik Seeley
wrote:
> On Tue, Mar 29, 2011 at 10:20 AM, Ryan McKinley wrote:
Another key example would be inline highlighting:
&id,_hl:title_,body
>>>
>>> If we're going to come up with another syntax, it needs to be fully fleshed
>>> out.
>>
On Tue, Mar 29, 2011 at 10:20 AM, Ryan McKinley wrote:
>>>
>>> Another key example would be inline highlighting:
>>>
>>> &id,_hl:title_,body
>>
>> If we're going to come up with another syntax, it needs to be fully fleshed
>> out.
>> This one already looks ambiguous in the context of "fl".
>>
>>
[
https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012502#comment-13012502
]
Upayavira commented on SOLR-2399:
-
It seems to me that the first task here is to reach a fe
+1
Walked through solr tutoral + example
Linked to a dependent project and all tests pass
On Sat, Mar 26, 2011 at 10:07 PM, Grant Ingersoll wrote:
> Artifacts are at http://people.apache.org/~gsingers/staging_area/rc3/.
> Please vote as you see appropriate. Vote closes on March 29th.
>
> I'
[
https://issues.apache.org/jira/browse/LUCENE-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012501#comment-13012501
]
RynekMedyczny.pl commented on LUCENE-2454:
--
{quote}
Code like this ends up in tr
>>
>> Another key example would be inline highlighting:
>>
>> &id,_hl:title_,body
>
> If we're going to come up with another syntax, it needs to be fully fleshed
> out.
> This one already looks ambiguous in the context of "fl".
>
> For example, does that mean give me "id","title highlighted","body
On Tue, Mar 29, 2011 at 10:08 AM, Ryan McKinley wrote:
>>>
>>> I was trying to think up what other real use cases actually where...
>>> because that really does have a bearing on if a new syntax should be
>>> developed, and what that syntax should look like.
>>>
>>
>> The use cases I can think of
>>
>> I was trying to think up what other real use cases actually where...
>> because that really does have a bearing on if a new syntax should be
>> developed, and what that syntax should look like.
>>
>
> The use cases I can think of are either very simple or very complex.
> I like this because i
On Tue, Mar 29, 2011 at 7:36 AM, Yonik Seeley
wrote:
> On Mon, Mar 28, 2011 at 11:26 PM, Ryan McKinley wrote:
>>>
>>> And I'm still on the fence - _explain_ alone does not justify a whole
>>> new syntax IMO... so we may need more usecase examples to figure out
>>> what problem we're actually tryi
[
https://issues.apache.org/jira/browse/SOLR-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012483#comment-13012483
]
Ryan McKinley commented on SOLR-2423:
-
fixed in #1086582
> FieldType can take Object r
[
https://issues.apache.org/jira/browse/LUCENE-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012476#comment-13012476
]
Andrzej Bialecki commented on LUCENE-2995:
---
+1 for a "suggester" module.
> fa
[
https://issues.apache.org/jira/browse/LUCENE-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012473#comment-13012473
]
Robert Muir commented on LUCENE-2995:
-
Grant should we call the module suggestor or s
On Tue, Mar 29, 2011 at 8:40 AM, Shai Erera wrote:
> I see. On the other hand, it's a bit annoying when you run with X=100 for
> the purpose of catching a multi-threaded bug, which occurs after the 2nd
> iteration ...
Yea I want both options too, just saying I want to somehow keep the
existing be
[
https://issues.apache.org/jira/browse/SOLR-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012465#comment-13012465
]
Ryan McKinley commented on SOLR-2423:
-
It is in TrieDateField
{code:java}
long time
[
https://issues.apache.org/jira/browse/LUCENE-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll reassigned LUCENE-2998:
---
Assignee: Grant Ingersoll
> Forward Port 3.1 Ant release tasks
> ---
1 - 100 of 115 matches
Mail list logo
