[
https://issues.apache.org/jira/browse/LUCENE-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008348#comment-13008348
]
Steven Rowe commented on LUCENE-2973:
-
Forgot to mention: the patch is against trunk.
[
https://issues.apache.org/jira/browse/LUCENE-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-2973:
Attachment: LUCENE-2973.patch
Renamed the directory in which {{svn export}} operates, from
{{buil
[
https://issues.apache.org/jira/browse/LUCENE-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-2973:
Attachment: LUCENE-2973.patch
Patch implementing the idea. {{svn info}} is used to collect the rev
Source distribution packaging targets should make a tarball from "svn export"
-
Key: LUCENE-2973
URL: https://issues.apache.org/jira/browse/LUCENE-2973
Project: Lucene - Java
[
https://issues.apache.org/jira/browse/SOLR-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008344#comment-13008344
]
Xing Li commented on SOLR-2432:
---
Once the solr.war is copied to webapps, star the app with
j
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6059/
1 tests failed.
REGRESSION: org.apache.solr.cloud.CloudStateUpdateTest.testCoreRegistration
Error Message:
null
Stack Trace:
junit.framework.AssertionFailedError:
at
org.apache.lucene.util.LuceneTestCase$Lu
Well you never saw how many that need to be sorted :) It is a pretty big
list.
On 3/17/11 12:20 PM, "Hoss Man (JIRA)" wrote:
>
>[
>https://issues.apache.org/jira/browse/SOLR-2431?page=com.atlassian.jira.pl
>ugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008049#comm
>ent-1300
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6058/
1 tests failed.
REGRESSION: org.apache.solr.cloud.BasicDistributedZkTest.testDistribSearch
Error Message:
Severe errors in solr configuration. Check your log files for more detailed
information on what may be wrong.
Build: https://hudson.apache.org/hudson/job/Lucene-trunk/1500/
All tests passed
Build Log (for compile errors):
[...truncated 16578 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands,
On Thu, Mar 17, 2011 at 11:18 PM, Chris Hostetter
wrote:
>
> : A 1.4.2 release in development, yes. That's the earliest point that
> : the bug was fixed, and someone
> : upgrading from 1.4.1 should look at everything after the 1.4.1 release.
>
> that makes no sense to me. even if a 1.4.2 release
On Mar 17, 2011, at 11:13 PM, Chris Hostetter wrote:
> patches welcome!
Sometimes you have to slash and burn to clean out the old under brush.
My patch would simply excise forrest and the website. Then, reveling in the
success of that great improvement, I'd sit back, take stalk and see what cam
: A 1.4.2 release in development, yes. That's the earliest point that
: the bug was fixed, and someone
: upgrading from 1.4.1 should look at everything after the 1.4.1 release.
that makes no sense to me. even if a 1.4.2 release is going ot exist at
some hypothetical point in the future, it doe
: one form to the other - but please, oh please, can we stop distributing
: the website in the release. Including the PDF's of the website. This is
: a pain in the ass to have to update and then include in the release as
: an RM - it's not worth its weight IMO. Disengage from Forrest ...
: dis
: The source is because I *think* we are required by the ASF to have
yes. we are.
: source for a release (but we can have as many other artifacts as we
: want to). Otherwise I'd say "yeah, dump the source release, use svn".
: Providing source releases as opposed to git or svn URLs is getting
:
On Thu, Mar 17, 2011 at 3:53 PM, Chris Hostetter
wrote:
> * CHANGES.txt has a "1.4.2-dev" section listing bug fixes ... as if that
> were a release after 1.4.1 and before the current 3.1 release.
A 1.4.2 release in development, yes. That's the earliest point that
the bug was fixed, and someone
u
[
https://issues.apache.org/jira/browse/SOLR-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008284#comment-13008284
]
Jayendra Patil commented on SOLR-2416:
--
This issue existed in Solr 1.4 packaged with T
On Mar 17, 2011, at 9:45 PM, Chris Hostetter wrote:
>
> by thta same rationale, we don't need to include javadocs in any release,
> because you could always find them online (and if i wanted to be snarky:
> you could always go find the java source itself online too)
I'm tempted to +1 both tho
On Thu, Mar 17, 2011 at 9:45 PM, Chris Hostetter
wrote:
> by thta same rationale, we don't need to include javadocs in any release,
> because you could always find them online (and if i wanted to be snarky:
> you could always go find the java source itself online too)
Absolutely.
The source is be
: IMO, I think our source release should be what you get when you do a
: checkout from SVN.
: Building from source is more expert level, and one needs (minimally) ant set
up.
meh. i don't really disagree with you, this is one of hte points i was
trying to make about wondering why we had two di
[
https://issues.apache.org/jira/browse/SOLR-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-2332:
---
Affects Version/s: (was: 4.0)
Fix Version/s: 3.2
I can't find any docs suggestion how exactly Tika
[
https://issues.apache.org/jira/browse/SOLR-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-2416:
---
Affects Version/s: (was: 4.0)
1.4.1
Fix Version/s: 3.2
Summary
IMO, I think our source release should be what you get when you do a
checkout from SVN.
Building from source is more expert level, and one needs (minimally) ant set up.
If I do another RC, I'm half-way convinced I should just do an "svn
export" and tar it up. No .zip... anyone handling a source r
: * nothing in README or "ant -p" about how to build the non-javadocs (ie:
: tutorial)
we could add a one liner about this to the README.txt...
Run the forrest command in the src/site directory to build the tutorial
...but the more i think about it the more i'm convinced that we should
[
https://issues.apache.org/jira/browse/SOLR-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-2434:
---
Attachment: SOLR-2434.patch
patch against trunk.
This seems pretty straight forward to me, i don't see any do
[
https://issues.apache.org/jira/browse/SOLR-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008223#comment-13008223
]
Yonik Seeley commented on SOLR-2434:
Unless it's very straightforward, we shouldn't muc
Rip out "ant init-forrest-entities" and the specversion variables from the
tutorial.xml
---
Key: SOLR-2434
URL: https://issues.apache.org/jira/browse/SOLR-2434
Projec
: I spent this morning reviewing the Solr tgz artifacts (will look at hte
: lucene ones after lunch). Notes so far...
Lucene Artifacts...
# General concerns
As mentioned before, there are a bunch of files only included in the src
release that seem suspicious -- they should probab
On Wed, Mar 16, 2011 at 10:13 PM, Chris Hostetter
wrote:
> %% diff -r s-bin-tgz/apache-solr-3.1.0/ s-src-tgz/apache-solr-3.1.0/solr/
>
> Binary files
> s-bin-tgz/apache-solr-3.1.0/contrib/analysis-extras/lucene-libs/lucene-icu-3.1.0.jar
> and
> s-src-tgz/apache-solr-3.1.0/solr/contrib/analy
[
https://issues.apache.org/jira/browse/LUCENE-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008175#comment-13008175
]
Paul Elschot commented on LUCENE-2968:
--
I had a look at the precedence parser. It wo
Make FieldProperties bit masks protected
Key: SOLR-2433
URL: https://issues.apache.org/jira/browse/SOLR-2433
Project: Solr
Issue Type: Improvement
Reporter: Ryan McKinley
Prior
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6048/
1 tests failed.
REGRESSION: org.apache.lucene.collation.TestCollationKeyAnalyzer.testThreadSafe
Error Message:
Java heap space
Stack Trace:
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copy
On Thu, Mar 17, 2011 at 3:53 PM, Chris Hostetter
wrote:
> [javadoc]
> /home/hossman/tmp/lucene3.1rc/3.1.rc1/s-src-tgz/apache-solr-3.1.0/solr/src/java/org/apache/solr/schema/IndexSchema.java:105:
> warning - Tag @link: can't find IndexSchema(SolrConfig, String,
> InputStream) in org.apache.solr.sc
Intermittent failure in TestFieldCacheTermsFilter.testMissingTerms
--
Key: LUCENE-2972
URL: https://issues.apache.org/jira/browse/LUCENE-2972
Project: Lucene - Java
Issue Type:
[
https://issues.apache.org/jira/browse/LUCENE-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008116#comment-13008116
]
Michael McCandless commented on LUCENE-2881:
bq. Mike would you be so kind an
On Mar 17, 2011, at 3:53 PM, Chris Hostetter wrote:
>
> * CHANGES.txt says we are using Tika 0.8-SNAPSHOT and UIMA 2.3.1-SNAPSHOT,
> but when i look at the actual jars there is no indication that these are
> snapshots...
It should be TIKA-0.8.
---
: This is just to make it easier for everyone to review the current
: state of the packages (there were a lot of minor fixups since RC0)
: and identify any other blockers.
I spent this morning reviewing the Solr tgz artifacts (will look at hte
lucene ones after lunch). Notes so far...
[
https://issues.apache.org/jira/browse/SOLR-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008073#comment-13008073
]
Ryan McKinley commented on SOLR-2423:
-
added to trunk in #1082638, after 3.1 is release
[
https://issues.apache.org/jira/browse/SOLR-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008049#comment-13008049
]
Hoss Man commented on SOLR-2431:
while this wouldn't be hard, it doesn't really seem like t
[
https://issues.apache.org/jira/browse/SOLR-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008041#comment-13008041
]
Otis Gospodnetic commented on SOLR-1986:
This looks useful. Thomas or Mark, would
Thanks for sharing this! - I tested it by sending a few mails and indeed it
works! - GMAIL threads detection seems to ignore the text within the
brackets. I wonder if such a change can be applied per project, or must be
applied for all projects.
Just opened https://issues.apache.org/jira/browse/INF
I will assume lazy consensus and commit changes to /trunk soon --
after 3.1 is released, I'll port and deprecate
On Wed, Mar 16, 2011 at 12:06 PM, Ryan McKinley wrote:
> any concerns with this proposal? If not, i would like to commit soon.
>
> After 3.1 is released, i would merge with 3.x branc
[
https://issues.apache.org/jira/browse/SOLR-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ahmet Arslan updated SOLR-1499:
---
Attachment: SOLR-1499.patch
Bring upto trunk version 1082579.
Add (format="javabin|xml") parameter. xm
[
https://issues.apache.org/jira/browse/SOLR-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll reassigned SOLR-1942:
-
Assignee: Grant Ingersoll
> Ability to select codec per field
> --
[
https://issues.apache.org/jira/browse/LUCENE-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007987#comment-13007987
]
Grant Ingersoll commented on LUCENE-2971:
-
Thanks for the pointers, that should d
[
https://issues.apache.org/jira/browse/LUCENE-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007964#comment-13007964
]
Yonik Seeley commented on LUCENE-2971:
--
We need to be careful about an auto generate
On Thu, Mar 17, 2011 at 11:30 AM, Grant Ingersoll wrote:
> If its ASL, it requires a NOTICE, is my understanding.
That's for a complete distribution, not every component of a distribution.
The NOTICE file is only for components which require special
attribution (so by some people's standards, we
If its ASL, it requires a NOTICE, is my understanding. Some of these are
admittedly redundant/overkill since we have a ton of ASF code in here, but I'd
like to keep a 1-1 for every jar, that way we know what every JAR is and
whether it requires one (see for instance all the commons jars). From
Auto Generate our LICENSE.txt and NOTICE.txt files
--
Key: LUCENE-2971
URL: https://issues.apache.org/jira/browse/LUCENE-2971
Project: Lucene - Java
Issue Type: Improvement
Reporter
[
https://issues.apache.org/jira/browse/LUCENE-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-2971:
Fix Version/s: 4.0
3.2
> Auto Generate our LICENSE.txt and NOTICE.txt f
On Thu, Mar 17, 2011 at 11:05 AM, wrote:
> Added: lucene/dev/trunk/solr/lib/servlet-api-NOTICE.txt
> URL:
> http://svn.apache.org/viewvc/lucene/dev/trunk/solr/lib/servlet-api-NOTICE.txt?rev=1082520&view=auto
> ==
> --- l
[
https://issues.apache.org/jira/browse/LUCENE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-2952:
Attachment: LUCENE-2952.patch
I think this is ready to go. It checks licenses, it checks
[
https://issues.apache.org/jira/browse/LUCENE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-2952:
Attachment: LUCENE-2952.patch
latest patch
> Make license checking/maintenance easier/aut
[
https://issues.apache.org/jira/browse/LUCENE-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer reassigned LUCENE-2881:
---
Assignee: Simon Willnauer (was: Michael Busch)
> Track FieldInfo per segment instea
[
https://issues.apache.org/jira/browse/LUCENE-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-2881:
Attachment: LUCENE-2881.patch
Attached next iteration.
* merged FieldInfoBiMap into Field
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6035/
1 tests failed.
REGRESSION:
org.apache.solr.client.solrj.embedded.SolrExampleStreamingTest.testCommitWithin
Error Message:
expected:<0> but was:<1>
Stack Trace:
junit.framework.AssertionFailedError: expected:<0> but
[
https://issues.apache.org/jira/browse/SOLR-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher reassigned SOLR-1499:
--
Assignee: (was: Erik Hatcher)
not an active area of development currently.
> SolrEntityProc
[
https://issues.apache.org/jira/browse/SOLR-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007919#comment-13007919
]
Erik Hatcher commented on SOLR-1499:
Seems like a parameter to the SolrEntityProcessor
[
https://issues.apache.org/jira/browse/SOLR-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007917#comment-13007917
]
Erik Hatcher commented on SOLR-2432:
Trunk sorting is working fine for me. Using the e
I will probably submit a patch to RAT at some point for this, but wanted to
prove it out here first as we have an immediate need and I don't want to wait
for a RAT release nor do I have the time to learn the RAT code at this point.
Others are welcome to port it.
-Grant
On Mar 17, 2011, at 1:
using sort option only returns numFound=1 even if there are many more matching
--
Key: SOLR-2432
URL: https://issues.apache.org/jira/browse/SOLR-2432
Project: Solr
I
[
https://issues.apache.org/jira/browse/LUCENE-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007901#comment-13007901
]
Grant Ingersoll commented on LUCENE-2968:
-
spn works for me, or simply ! maybe.
hi all
I read the the Lucene Google Summer of Code 2011 at
http://wiki.apache.org/lucene-java/SummerOfCode2011. document
identifier reassignment
could make index smaller. even simply sorting documents by url will
achieve many benifits. There are many research papers about this
topic. Maybe
we
[
https://issues.apache.org/jira/browse/LUCENE-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007883#comment-13007883
]
Michael McCandless commented on LUCENE-2962:
I think this paper is relevant:
63 matches
Mail list logo
