[
https://issues.apache.org/jira/browse/LUCENE-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029150#comment-13029150
]
Doron Cohen commented on LUCENE-3068:
-
This is more complex than I originally thought
I'm not sure you will find anyone wanting to put in this effort now, but
another suggestion for a general approach might be:
1 very basic static analysis to catch what you can - this should be a
pretty minimal effort only given what can reasonably be achieved
2 throw runtime errors as Hoss sa
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029075#comment-13029075
]
Yonik Seeley commented on SOLR-2493:
Ryan: yep... +1 to all that.
> SolrQueryParser co
[
https://issues.apache.org/jira/browse/LUCENE-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3070:
Attachment: LUCENE-3070.patch
first taking a look at the branch, just a really quick hack at a pat
As a rule, everything should go through JIRA on its way to svn -- this
is important so that we have somewhere to point for why we did things.
Even small things.
With patches from contributors it is especially important they are
added to JIRA because they need to grant the license to ASF. Also
at
[
https://issues.apache.org/jira/browse/LUCENE-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029034#comment-13029034
]
Hoss Man commented on LUCENE-1418:
--
David: i agree with you that QueryParser should be u
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029028#comment-13029028
]
Ryan McKinley commented on SOLR-2493:
-
bq. I thought Solr's backwards policy is about p
A correction:
I wrote:
> The full artifact name would be org.apache.solr:apache-solr:,
> which seems weird to me in the double inclusion of "maven".
s/"maven"/"apache"/
: This looks compelling! I'm also not sure what, specifically, we can
: validate in Solr's configuration... and I also don't know how much
: validation we do today. What hard errors does Solr produce on startup
: when configuration is wrong?
once upon a time solr would log some config errors, bu
Hi Ryan,
> Do you want to make a JIRA issue with a patch?
>
> This is a good example of a patch that is easy to get committed
> quickly because it is simple, clear, and understandable.
Earlier today on #lucene IRC, David described the changes he had in mind, and
asked me where to put the patch,
Hi David,
> I thought I'd put together a list of interesting differences between the
> ant build output and the maven build output. Before each build I did a
> full clean and then after the build I saved a file listing to a text file
> so that I could diff it.
Cool! Thanks for the effort.
> 1.
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029018#comment-13029018
]
Uwe Schindler commented on SOLR-2493:
-
Ryan: I agree, this is why I always bring this u
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3065:
--
Issue Type: Improvement (was: Bug)
> NumericField should be stored in binary format in index
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3065:
--
Attachment: (was: LUCENE-3065-solr-only.patch)
> NumericField should be stored in binary f
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029011#comment-13029011
]
Uwe Schindler commented on LUCENE-3065:
---
I started a new issue in Solr for the chan
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3065:
--
Comment: was deleted
(was: Here a first step in cutover of Solr to NumericField. Most tests wo
[
https://issues.apache.org/jira/browse/SOLR-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated SOLR-2497:
Attachment: SOLR-2497.patch
Patch applies to 3.2 branch only and needs the patch from LUCENE-3065 ap
Move Solr to new NumericField stored field impl of LUCENE-3065
--
Key: SOLR-2497
URL: https://issues.apache.org/jira/browse/SOLR-2497
Project: Solr
Issue Type: Improvement
Do you want to make a JIRA issue with a patch?
This is a good example of a patch that is easy to get committed
quickly because it is simple, clear, and understandable.
ryan
On Wed, May 4, 2011 at 5:41 PM, Smiley, David W. wrote:
> Steve Row,
>
> I thought I'd put together a list of interesting
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029003#comment-13029003
]
Ryan McKinley commented on SOLR-2493:
-
bq. I was also really confused about the design
[
https://issues.apache.org/jira/browse/SOLR-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028999#comment-13028999
]
Yonik Seeley commented on SOLR-2496:
Yeah, I agree we should be able to add multiple do
[
https://issues.apache.org/jira/browse/SOLR-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neil Hooey updated SOLR-2496:
-
Description:
The following is the current Solr 3.1 format for sending multiple documents by
JSON. It's no
[
https://issues.apache.org/jira/browse/SOLR-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neil Hooey updated SOLR-2496:
-
Remaining Estimate: (was: 4h)
Original Estimate: (was: 4h)
> JSON Update Handler doesn't hand
[
https://issues.apache.org/jira/browse/SOLR-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neil Hooey updated SOLR-2496:
-
Description:
The following is the current Solr 3.1 format for sending multiple
documents by JSON. It's not
JSON Update Handler doesn't handle multiple docs properly
-
Key: SOLR-2496
URL: https://issues.apache.org/jira/browse/SOLR-2496
Project: Solr
Issue Type: Bug
Components: updat
[
https://issues.apache.org/jira/browse/SOLR-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-2495.
Resolution: Fixed
> update noggit json parser
> -
>
> Key: S
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028989#comment-13028989
]
Uwe Schindler commented on SOLR-2493:
-
We should not again fight here against each othe
Steve Row,
I thought I'd put together a list of interesting differences between the ant
build output and the maven build output. Before each build I did a full clean
and then after the build I saved a file listing to a text file so that I could
diff it.
I'm using svn revision 1087373 (March 3
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028986#comment-13028986
]
Yonik Seeley commented on SOLR-2493:
bq. How is that obvious?
The signature of these m
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028980#comment-13028980
]
Uwe Schindler commented on SOLR-2493:
-
bq. I rather actually wonder why the config is n
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028975#comment-13028975
]
Uwe Schindler edited comment on SOLR-2493 at 5/4/11 9:32 PM:
-
b
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028975#comment-13028975
]
Uwe Schindler commented on SOLR-2493:
-
bq. The cause of the problem came from needing p
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028974#comment-13028974
]
Stephane Bailliez commented on SOLR-2493:
-
The problem is hardly about naming here,
make compoundfilewriter public
--
Key: LUCENE-3073
URL: https://issues.apache.org/jira/browse/LUCENE-3073
Project: Lucene - Java
Issue Type: Improvement
Reporter: Robert Muir
Priority: Mino
[
https://issues.apache.org/jira/browse/LUCENE-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3073:
Attachment: LUCENE-3073.patch
> make compoundfilewriter public
> --
>
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028954#comment-13028954
]
Robert Muir commented on SOLR-2493:
---
{quote}
All of the "get" methods on the Config class
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028943#comment-13028943
]
Hoss Man commented on SOLR-2493:
bq. this is solr's fault by having a getter that does some
On May 2, 2011, at 7:54 PM, Chris Hostetter wrote:
> We should definitely kill of "Next" ... i would suggest just removing it,
> and not bulk applying a new version (there is no requirement that issues
> have a version)
Chris, in JIRA, "Next" has this description:
> Placeholder for commiters
update noggit json parser
-
Key: SOLR-2495
URL: https://issues.apache.org/jira/browse/SOLR-2495
Project: Solr
Issue Type: Bug
Reporter: Yonik Seeley
Assignee: Yonik Seeley
Fix For:
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3065:
--
Attachment: LUCENE-3065-solr-only.patch
Here a first step in cutover of Solr to NumericField.
[
https://issues.apache.org/jira/browse/LUCENE-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen updated LUCENE-3068:
Attachment: LUCENE-3068.patch
Attached modified version of the test - one that invokes the query p
[
https://issues.apache.org/jira/browse/LUCENE-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028895#comment-13028895
]
Doron Cohen commented on LUCENE-3068:
-
bq. specifically when the doc itself has token
Error in Context.setSessionAttribute implementation (ContextImpl.putVal)
Key: SOLR-2494
URL: https://issues.apache.org/jira/browse/SOLR-2494
Project: Solr
Issue Type: B
[
https://issues.apache.org/jira/browse/LUCENE-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-3072.
-
Resolution: Fixed
Fix Version/s: 4.0
3.2
Committed revision 1099529, 1
[
https://issues.apache.org/jira/browse/SOLR-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-2462:
---
Attachment: SOLR-2462_3_1.patch
The original patch would not apply cleanly for me against 3.1 without
[
https://issues.apache.org/jira/browse/LUCENE-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028822#comment-13028822
]
Michael McCandless commented on LUCENE-3072:
Looks good Robert, nice catch!
[
https://issues.apache.org/jira/browse/LUCENE-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3072:
Attachment: LUCENE-3072.patch
> 3.1 fileformats out of date
> ---
>
>
3.1 fileformats out of date
---
Key: LUCENE-3072
URL: https://issues.apache.org/jira/browse/LUCENE-3072
Project: Lucene - Java
Issue Type: Bug
Reporter: Robert Muir
Attachments: LUCENE-3072.patch
PathHierarchyTokenizer adaptation for urls: splits reversed
---
Key: LUCENE-3071
URL: https://issues.apache.org/jira/browse/LUCENE-3071
Project: Lucene - Java
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028798#comment-13028798
]
Michael McCandless commented on LUCENE-3018:
That sounds good for starters?
Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/7719/
No tests ran.
Build Log (for compile errors):
[...truncated 35 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional c
Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/7718/
No tests ran.
Build Log (for compile errors):
[...truncated 46 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional
Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/7717/
No tests ran.
Build Log (for compile errors):
[...truncated 19 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional
Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/7718/
No tests ran.
Build Log (for compile errors):
[...truncated 81 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional c
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028764#comment-13028764
]
Uwe Schindler edited comment on LUCENE-3065 at 5/4/11 2:44 PM:
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3065:
--
Attachment: LUCENE-3065.patch
I added some javadocs to Document class:
- getField() / getField
Enable DocValues by default for every Codec
---
Key: LUCENE-3070
URL: https://issues.apache.org/jira/browse/LUCENE-3070
Project: Lucene - Java
Issue Type: Task
Components: Index
Affects V
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028757#comment-13028757
]
Simon Willnauer commented on LUCENE-3018:
-
bq. OK, if I change the /linux to /sol
[
https://issues.apache.org/jira/browse/LUCENE-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-3069:
Summary: Lucene should have an entirely memory resident term dictionary
(was: Lucene shou
Lucene should be able to have a entirely memory resident term dictionary
Key: LUCENE-3069
URL: https://issues.apache.org/jira/browse/LUCENE-3069
Project: Lucene - Java
On Wed, May 4, 2011 at 3:49 PM, Mark Miller wrote:
>
> On May 4, 2011, at 9:42 AM, Uwe Schindler wrote:
>
>> Solr has no performance testing framework, see the issue from today
>> (SOLR-2493).
>
> Come to Berlin Buzzwords!
I think I will come :)
simon
>
> (I know you already are :) )
>
> - Mark M
On May 4, 2011, at 9:42 AM, Uwe Schindler wrote:
> Solr has no performance testing framework, see the issue from today
> (SOLR-2493).
Come to Berlin Buzzwords!
(I know you already are :) )
- Mark Miller
lucidimagination.com
Lucene/Solr User Conference
May 25-26, San Francisco
www.lucenerevol
> From: Robert Muir [mailto:rcm...@gmail.com]
> Sent: Wednesday, May 04, 2011 3:30 PM
> To: dev@lucene.apache.org
> Subject: Re: modularization discussion
>
> On Wed, May 4, 2011 at 9:11 AM, Mark Miller
> wrote:
> > Side note (plug): I have been playing with the benchmark module (who did
> that m
On Wed, May 4, 2011 at 9:11 AM, Mark Miller wrote:
> Side note (plug): I have been playing with the benchmark module (who did that
> module? I had missed it), and I've got some cool stuff to show at Berlin
> Buzzwords this year for my solr performance talk!
>
we svn move'd it here: https://issu
On May 4, 2011, at 8:25 AM, Michael McCandless wrote:
> Mark,
>
> Can you give some more details on your disagreement here...?
>
> Are there certain modules from my list that you don't think should be
> modules? The timeframe (1-2 years) is too optimistic/aggressive? Or
> you disagree that we
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028738#comment-13028738
]
Michael McCandless commented on LUCENE-3018:
OK, if I change the /linux to /s
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028736#comment-13028736
]
Chris Male commented on SOLR-2493:
--
bq. In my opinion, the correct way to solve this is to
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028734#comment-13028734
]
Robert Muir commented on SOLR-2493:
---
{quote}
In my opinion, the correct way to solve this
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028733#comment-13028733
]
Michael McCandless commented on LUCENE-3065:
Patch looks great Uwe!
I think
>
> if anyone disagree that we should move Solr to more strict error
> checking of its configuration on startup. I think being silent on
> configuration errors is the wrong choice... and I think that's
+1 for validation/ warning/ error messages from config files. Excellent
link, Michael (Sokolov
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028729#comment-13028729
]
Uwe Schindler commented on SOLR-2493:
-
In my opinion, the correct way to solve this is
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028728#comment-13028728
]
Uwe Schindler commented on SOLR-2493:
-
...as I said before :-)
> SolrQueryParser const
Mark,
Can you give some more details on your disagreement here...?
Are there certain modules from my list that you don't think should be
modules? The timeframe (1-2 years) is too optimistic/aggressive? Or
you disagree that we should poach from outside projects too...?
Or, more generally, you d
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028727#comment-13028727
]
Robert Muir commented on SOLR-2493:
---
this wasn't broken by the lucene commit.
this is so
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3065:
--
Attachment: LUCENE-3065.patch
Moved test to TestFieldsReader
> NumericField should be stored
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reassigned LUCENE-3065:
-
Assignee: Uwe Schindler
> NumericField should be stored in binary format in index (match
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028718#comment-13028718
]
Uwe Schindler commented on LUCENE-3065:
---
Just to note: We also need to change the F
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3065:
--
Attachment: LUCENE-3065.patch
Next iteration:
Reverted changes in Solr (they should come late
Solr-cell references boilerpipe 1.1.0 which contains a modified version
of nekohtml 1.9.9.
It seems that this version of nekohtml is broken in that it references
the class LostText without including it.
The unmodified release of nekohtml 1.9.9 does not reference or include
this class and the la
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028707#comment-13028707
]
Uwe Schindler edited comment on LUCENE-3065 at 5/4/11 11:06 AM:
---
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3065:
--
Attachment: LUCENE-3065.patch
This patch adds some refactoring because FieldSelectorResult is
Hi Uwe,
do you mean one issue per GSoC proposal, or one for every logical "unit" in
the project?
If the second: Robert told me to use the flexscoring branch as a base for my
project, since preliminary work has already been done in that branch. Should I
open JIRA issues nevertheless?
Thanks,
D
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3065:
--
Attachment: (was: LUCENE-3065.patch)
> NumericField should be stored in binary format in i
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3065:
--
Attachment: LUCENE-3065.patch
New patch, previous one had a leftover unused constant from Mike
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3065:
--
Attachment: LUCENE-3065.patch
More refactoring:
- Now NumericFields also reproduce the indexed
Hi Michael,
This looks compelling! I'm also not sure what, specifically, we can
validate in Solr's configuration... and I also don't know how much
validation we do today. What hard errors does Solr produce on startup
when configuration is wrong?
I know one challenge is the fact that plugins can
[
https://issues.apache.org/jira/browse/LUCENE-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen reassigned LUCENE-3068:
---
Assignee: Doron Cohen
> The repeats mechanism in SloppyPhraseScorer is broken when doc has t
[
https://issues.apache.org/jira/browse/LUCENE-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3068:
---
Attachment: LUCENE-3068.patch
Patch w/ test case showing the problem.
If you set sl
The repeats mechanism in SloppyPhraseScorer is broken when doc has tokens at
same position
--
Key: LUCENE-3068
URL: https://issues.apache.org/jira/browse/LUCENE-3068
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028693#comment-13028693
]
Michael McCandless commented on LUCENE-3065:
Patch looks great Uwe! Except w
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3065:
--
Attachment: LUCENE-3065.patch
Here the patch with my changes
> NumericField should be stored
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028689#comment-13028689
]
Michael McCandless commented on LUCENE-3018:
Patch works well for me -- I ins
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028680#comment-13028680
]
Uwe Schindler commented on LUCENE-3065:
---
This gives us more freedom in future, as w
[
https://issues.apache.org/jira/browse/LUCENENET-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-413:
---
Attachment: MediumTrust.2.9.4.patch
constants.cs fix added into patch
> Medium trust security issue
> -
[
https://issues.apache.org/jira/browse/LUCENE-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028677#comment-13028677
]
Uwe Schindler commented on LUCENE-3065:
---
Mike:
I reviewed the patch again: You are
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker updated LUCENE-3018:
--
Attachment: LUCENE-3018.patch
I have made the changes mentioned above.
> Lucene Native Direc
Hi Vinicius,
Submitting patches via JIRA is fine! We were just thinking about possibly
providing some SVN to work with (as additional "training"), but came to the
conclusion, that all students should go the "standard" Apache Lucene way of
submitting patches to JIRA issues. You can of course sti
hey folks,
BerlinBuzzwords 2011 is close only 33 days left until the big Search,
Store and Scale opensource crowd is gathering
in Berlin on June 6th/7th.
The conference again focuses on the topics search,
data analysis and NoSQL. It is to take place on June 6/7th 2011 in Berlin.
We are looking f
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028649#comment-13028649
]
Simon Willnauer commented on LUCENE-3018:
-
hey varun
sorry for the long delay! I
[
https://issues.apache.org/jira/browse/SOLR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated SOLR-2493:
Attachment: (was: SOLR-2493-3.x.patch)
> SolrQueryParser constantly parse luceneMatchVersion in
1 - 100 of 102 matches
Mail list logo
