[
https://issues.apache.org/jira/browse/SOLR-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139997#comment-13139997
]
JohnWu edited comment on SOLR-1395 at 12/30/11 6:49 AM:
tom：
For
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x/11965/
2 tests failed.
REGRESSION: org.apache.solr.client.solrj.SolrExampleBinaryTest.testCommitWithin
Error Message:
expected:<1> but was:<0>
Stack Trace:
junit.framework.AssertionFailedError: expected:<1> but was:<0>
at
[
https://issues.apache.org/jira/browse/SOLR-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177561#comment-13177561
]
Brooke Schreier Ganz commented on SOLR-2982:
Thank you so much for working on t
Build: https://builds.apache.org/job/Lucene-trunk/1784/
3 tests failed.
REGRESSION: org.apache.lucene.index.TestDuelingCodecs.testEquals
Error Message:
Java heap space
Stack Trace:
java.lang.OutOfMemoryError: Java heap space
at org.apache.lucene.util.ArrayUtil.grow(ArrayUtil.java:338)
Unfortunately, my desires for this project seem to change with the progress
that we make on it. What I mean, is that what I want right now, will
likely be different from what I will want once we've released a few more
versions. What I KNOW I want right now:
I want the line-by-line port to contin
To make it clear - I want a .Net idiomatic API as the only API. I've got
experience with both kinds of APIs - strict transliterated from Java and
translated from Java to .Net. For me, the choice is pretty clear - the
latter has the advantage when it comes to long-term maintenance and support
from .
I completely agree with Michael's mentality on thinking of this as a
business and coming from the perspective of "what will wow our
customers" ...
I also completely agree with Prescott, that we just need to get down
to brass tacks and say what we want it to be specifically and
subjectively.
Here'
Some fixes might already be in trunk, the 2.9.4g branch and even the 3.0.3
branch. I can tell you that the code that the 3.0.3 branch was ported from
was the downloadable source, sometime around september/october and not
directly from SVN. Assuming that Lucene's Jira is correct, then all issues
t
[
https://issues.apache.org/jira/browse/SOLR-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177517#comment-13177517
]
Bill Bell commented on SOLR-2804:
-
We are having this issue as well
NFO: Wrote last indexe
[
https://issues.apache.org/jira/browse/LUCENE-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe resolved LUCENE-3655.
-
Resolution: Fixed
Fix Version/s: 3.6
> Add Maven artifact checks to dev-tools/scripts
Someone has to take a stand and call out what they prefer - rather than
shooting out all the alternatives, we need to start voicing our opinions of
which direction we need to go. I'll get us started: I want to see something
that is more .NET like, I want to see something that can run on the pho
Might I suggest that we all approach this as a business owners, community
builders, startup entrepreneurs instead of developers for a second.
You have limited resources: time, budget, personnel, etc.
What is our two biggest metrics of success for this product?
My guess is adoption and customer i
The other option for people not wanting a line-by-line port is to just
stick with whichever the last version that had a line-by-line
transliteration done to it. This is done in a number of projects where new
versions break compatibility. 2.9.4 is certainly a nice release...
-r
On Thu, Dec 29, 201
[
https://issues.apache.org/jira/browse/LUCENE-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-3655:
Attachment: LUCENE-3655.patch
In this version of the patch: under Cygwin, the classpath separator
Thinking about it, I should make myself more clear regarding why I
brought up IKVM again, just so no one gets the wrong idea about my
intentions there...
I only mentioned it as a justification for dropping line-by-line
compatibility and as an alternative for people who really care about
that. As w
[
https://issues.apache.org/jira/browse/SOLR-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-2992:
---
Attachment: SOLR-2992.patch
Here's a patch that adds support for specifying prepareCommit=true to upda
Apologies upfront: another long email.
My most firm opinion on this topic is that, as a community, we spend
too much time on this discussion. We should just simply commit to one
or the other path, or both, or some middle ground, or just commit to
not discussing it anymore and go with "whatever cod
I dont think at the end of the day we want to make just cosmetic changes. We
also have the issue of same name different casing which needs to be fixed - but
it's not clear how to manage that without some large adjustments to the API.
Sent from my Windows Phone
[
https://issues.apache.org/jira/browse/LUCENE-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177427#comment-13177427
]
Joe Cabrera commented on LUCENE-2987:
-
Currently the grammar accepts conjunctions AND
My vote goes to merging the two:
Apply the same concepts from 2.9.4g to 3.X development, using generics
where possible, Disposable vs Close, and exposing *additional* APIs
for generics (but leaving the existing old ones) to enable the
underlying performance improvements the generics offer. Also, e
I agree its a matter of taste. I'd vote continue with g and evolve it to where
we want a .net version to be. What do others think?
Sent from my Windows Phone
From: Digy
Sent: 12/29/2011 1:16 PM
To: lucene-net-...@lucene.apache.org
Subject: RE: [Lucene.Net] Lucene.
Digy looks like the diff from 2.9.4 is missing a couple of these. Do you mind
taking a second glance at that to make sure it's up to date? One of the things
we were dinged for was not having a good changelog. The g change log is already
better than we had for the trunk, but it doesn't hurt to gi
[
https://issues.apache.org/jira/browse/LUCENENET-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177420#comment-13177420
]
Prescott Nasser commented on LUCENENET-458:
---
I followed this thread when it w
[
https://issues.apache.org/jira/browse/LUCENENET-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prescott Nasser closed LUCENENET-459.
-
Resolution: Fixed
Assignee: Digy
> Italian stemmer (from SnowballAnalyzer) d
[
https://issues.apache.org/jira/browse/LUCENENET-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prescott Nasser updated LUCENENET-337:
--
Fix Version/s: (was: Lucene.Net 2.9.4)
Lucene.Net 3.x
Did not
[
https://issues.apache.org/jira/browse/LUCENENET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prescott Nasser resolved LUCENENET-391.
---
Resolution: Not A Problem
This is a separate project, can be found at bit bucket
[
https://issues.apache.org/jira/browse/LUCENENET-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prescott Nasser resolved LUCENENET-407.
---
Resolution: Fixed
Assignee: michael herndon
Michael added the necessary .snk
[
https://issues.apache.org/jira/browse/LUCENENET-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prescott Nasser closed LUCENENET-407.
-
> Signing the assembly
>
>
> Key: LUCENENET-407
>
[
https://issues.apache.org/jira/browse/LUCENENET-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prescott Nasser updated LUCENENET-372:
--
Fix Version/s: (was: Lucene.Net 2.9.4)
Didn't make it for 2.9.4
[
https://issues.apache.org/jira/browse/LUCENENET-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prescott Nasser updated LUCENENET-167:
--
Fix Version/s: (was: Lucene.Net 2.9.4)
> Compact Framework & Silverlight Sup
[
https://issues.apache.org/jira/browse/LUCENENET-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prescott Nasser updated LUCENENET-179:
--
Fix Version/s: (was: Lucene.Net 2.9.4)
> SnowballFilter speed improvment
> -
[
https://issues.apache.org/jira/browse/LUCENENET-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177408#comment-13177408
]
Prescott Nasser commented on LUCENENET-179:
---
Has anyone taken a look at this
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/11948/
1 tests failed.
REGRESSION: org.apache.solr.cloud.ZkControllerTest.testUploadToCloud
Error Message:
KeeperErrorCode = ConnectionLoss for /configs/config1/solrconfig-delpolicy1.xml
Stack Trace:
org.apache.zookeeper.KeeperEx
I forgot to mention, 2.9.4g implements IDisposable for many of the classes
that has a "Close()" method
which can be thought as .Net friendly API.
DIGY
-Original Message-
From: Scott Lombard [mailto:lombardena...@gmail.com]
Sent: Thursday, December 29, 2011 5:05 PM
To: lucene-net-...
When I started that "g" branch, I had no intention to change the API, but at
the end it resulted in a few changes
like StopAnalyzer(List stopWords),
Query.ExtractTerms(ICollection) etc.
But I think, a drop-in replacement will work for most of the Lucene.Net
users (Of course some contribs have been
[
https://issues.apache.org/jira/browse/SOLR-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177384#comment-13177384
]
Fabian Deutsch commented on SOLR-1954:
--
Good day, is there any progress on this or any
Might some of these fixes already be in the Lucene.Net codebase? For
example, when I looked at the subversion commits for
https://issues.apache.org/jira/browse/LUCENE-2620 I found that the changes
appear already in both the trunk and in the 2.9.4g branch. I'm not sure of
the provenance of the curre
SolrJ commit still has the flush parameter, it should be removed, and
softcommit should be added.
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[
https://issues.apache.org/jira/browse/SOLR-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177345#comment-13177345
]
Martijn van Groningen commented on SOLR-2990:
-
To me this seems like an apache
[
https://issues.apache.org/jira/browse/SOLR-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177304#comment-13177304
]
Rob Tulloh commented on SOLR-2990:
--
Opened tika ticket https://issues.apache.org/jira/brow
[
https://issues.apache.org/jira/browse/SOLR-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177301#comment-13177301
]
Rob Tulloh commented on SOLR-2990:
--
I'll open a ticket against tika for this issue. I'll a
[
https://issues.apache.org/jira/browse/SOLR-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177297#comment-13177297
]
Rob Tulloh commented on SOLR-2990:
--
Looks reproducible when I downloaded tika-app-1.0.jar.
[
https://issues.apache.org/jira/browse/SOLR-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177295#comment-13177295
]
James Dyer commented on SOLR-2993:
--
Also included with the patch are several new unit test
[
https://issues.apache.org/jira/browse/SOLR-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-2993:
-
Attachment: SOLR-2993.patch
Patch adds features described in this issue. Users can create a Dictionary
c
[
https://issues.apache.org/jira/browse/SOLR-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177290#comment-13177290
]
Hoss Man commented on SOLR-2990:
have you tried parsing these docs using tika on the comman
Integrate WordBreakSpellChecker with Solr
-
Key: SOLR-2993
URL: https://issues.apache.org/jira/browse/SOLR-2993
Project: Solr
Issue Type: Improvement
Components: SolrCloud, spellchecker
A
[
https://issues.apache.org/jira/browse/LUCENE-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated LUCENE-3523:
---
Attachment: LUCENE-3523.patch
This version adds a feature giving users more control over which words
add prepareCommit
-
Key: SOLR-2992
URL: https://issues.apache.org/jira/browse/SOLR-2992
Project: Solr
Issue Type: New Feature
Reporter: Yonik Seeley
Priority: Minor
Expose Lucene's prepareCommit to S
[
https://issues.apache.org/jira/browse/SOLR-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned SOLR-1998:
-
Assignee: (was: Mark Miller)
I never did look at this it seems - whoops - I doubt I'll go back
[
https://issues.apache.org/jira/browse/SOLR-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177264#comment-13177264
]
Mark Miller commented on SOLR-2633:
---
Cool - thanks Edoardo - look forward to it.
In 3X, not used consistently in all places Directory objects are
instantiated
-
Key: SOLR-2991
URL: https://issues.apache.org/jira/browse/SOLR-2991
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-2654.
---
Resolution: Fixed
> not used consistently in all places Directory objects are
> instantiated
> -
[
https://issues.apache.org/jira/browse/SOLR-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177259#comment-13177259
]
Mark Miller commented on SOLR-2654:
---
I don't think there is enough gain to tackle somethi
[
https://issues.apache.org/jira/browse/SOLR-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-2654:
--
Fix Version/s: (was: 3.6)
> not used consistently in all places Directory objects are
> instan
[
https://issues.apache.org/jira/browse/SOLR-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177258#comment-13177258
]
Rob Tulloh commented on SOLR-2990:
--
I have another document that causes OOM in a batch, bu
[
https://issues.apache.org/jira/browse/SOLR-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177257#comment-13177257
]
Mark Miller commented on SOLR-2805:
---
Here is an up to date example of using the tool (run
[
https://issues.apache.org/jira/browse/SOLR-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177254#comment-13177254
]
Mark Miller commented on SOLR-2806:
---
This is implemented in the solrcloud branch.
[
https://issues.apache.org/jira/browse/SOLR-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-2979.
---
Resolution: Duplicate
> ShowFileRequestHandler should really also work with config files in ZooKee
[
https://issues.apache.org/jira/browse/SOLR-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177252#comment-13177252
]
Mark Miller commented on SOLR-2722:
---
I've been doing this in the solrcloud branch - it wi
[
https://issues.apache.org/jira/browse/SOLR-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177249#comment-13177249
]
Mark Miller commented on SOLR-2616:
---
Sorry about the delay - I'm going to try to tackle t
I don't see the g branch differing all that much from the line-by-line port.
All the g branch does is change some data types as generics, but line by
line the code the same once the generics are declared.
I don't see 2.9.4g being any closer to a .NET style version than 2.9.4.
While it does gene
[
https://issues.apache.org/jira/browse/SOLR-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177215#comment-13177215
]
Rob Tulloh commented on SOLR-2990:
--
I successfully isolated one document that causes an OO
[
https://issues.apache.org/jira/browse/SOLR-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177209#comment-13177209
]
Rob Tulloh commented on SOLR-2990:
--
I will attempt to isolate some content that causes OOM
[
https://issues.apache.org/jira/browse/SOLR-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177207#comment-13177207
]
Martijn van Groningen commented on SOLR-2990:
-
I have had cases where large fil
[
https://issues.apache.org/jira/browse/SOLR-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177199#comment-13177199
]
Rob Tulloh commented on SOLR-2990:
--
Here is an example of a batch containing 1 document th
Some tokenfilters rely upon interned Types
--
Key: LUCENE-3669
URL: https://issues.apache.org/jira/browse/LUCENE-3669
Project: Lucene - Java
Issue Type: Task
Reporter: Robert Muir
at leas
[
https://issues.apache.org/jira/browse/LUCENE-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177201#comment-13177201
]
Robert Muir commented on LUCENE-2906:
-
I created LUCENE-3669 for the broader interned
Build: https://builds.apache.org/job/Lucene-Solr-Maven-3.x/346/
No tests ran.
Build Log (for compile errors):
[...truncated 22798 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e
[
https://issues.apache.org/jira/browse/SOLR-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177192#comment-13177192
]
Rob Tulloh commented on SOLR-2990:
--
In this particular test, we are using 2 threads to fee
[
https://issues.apache.org/jira/browse/LUCENE-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177187#comment-13177187
]
Robert Muir commented on LUCENE-2906:
-
Hi Uwe:
Many filters in lucene currently do t
[
https://issues.apache.org/jira/browse/SOLR-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177181#comment-13177181
]
Martijn van Groningen commented on SOLR-2990:
-
What is the average size of the
solr OOM issues
---
Key: SOLR-2990
URL: https://issues.apache.org/jira/browse/SOLR-2990
Project: Solr
Issue Type: Bug
Components: clients - java
Affects Versions: 4.0
Environment: CentOS 5.x/6.x
Solr Build
[
https://issues.apache.org/jira/browse/SOLR-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177153#comment-13177153
]
Erick Erickson commented on SOLR-1931:
--
bq: What if one is looking at a completely opt
[
https://issues.apache.org/jira/browse/SOLR-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sami Siren updated SOLR-2880:
-
Attachment: SOLR-2880.patch
another patch: got rid of CoreAssignment - ZkController now receives shardids
[
https://issues.apache.org/jira/browse/LUCENE-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177097#comment-13177097
]
Uwe Schindler edited comment on LUCENE-2906 at 12/29/11 10:44 AM:
-
[
https://issues.apache.org/jira/browse/LUCENE-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177101#comment-13177101
]
Uwe Schindler commented on LUCENE-2906:
---
...alternatively, we could use a HashSet.
[
https://issues.apache.org/jira/browse/LUCENE-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177097#comment-13177097
]
Uwe Schindler commented on LUCENE-2906:
---
Hi Robert,
I had no time to review before
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x/11956/
1 tests failed.
REGRESSION:
org.apache.solr.client.solrj.embedded.SolrExampleStreamingBinaryTest.testCommitWithin
Error Message:
expected:<1> but was:<0>
Stack Trace:
junit.framework.AssertionFailedError: expected:<1> but w
78 matches
Mail list logo
