Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.2/7/
All tests passed
Build Log:
[...truncated 10373 lines...]
[junit4] JVM J1: stdout was not empty, see:
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-NightlyTests-5.2/solr/build/solr-core/test/temp/junit4-J1-20150531_005833_
[
https://issues.apache.org/jira/browse/SOLR-7406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566372#comment-14566372
]
ASF subversion and git services commented on SOLR-7406:
---
Commit 16826
[
https://issues.apache.org/jira/browse/SOLR-7406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566356#comment-14566356
]
ASF subversion and git services commented on SOLR-7406:
---
Commit 16826
[
https://issues.apache.org/jira/browse/SOLR-7406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566353#comment-14566353
]
ASF subversion and git services commented on SOLR-7406:
---
Commit 16826
It’d be nice if something like that failed the build. There’s kind of a
soft dependency there for Solr’s logging admin screen, which is optional.
~ David
On Sun, May 31, 2015 at 12:45 AM Tomás Fernández Löbbe <
tomasflo...@gmail.com> wrote:
> Unfortunately I imported log4j Logger instead of sl
Unfortunately I imported log4j Logger instead of slf4j in SOLR-7406. I'll
fix this and merge it in the 5.2 branch. I think this should be a blocker
since it would require people to have the log4j jars.
On Fri, May 29, 2015 at 4:04 PM, Timothy Potter
wrote:
> +1 SUCCESS! [0:53:16.298079]
>
> Woot
[
https://issues.apache.org/jira/browse/SOLR-7406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomás Fernández Löbbe reopened SOLR-7406:
-
Reopen for changing import to slf4j
> Support DV implementation in range faceting
> --
[
https://issues.apache.org/jira/browse/LUCENE-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566312#comment-14566312
]
ASF subversion and git services commented on LUCENE-6487:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-7555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Pugh updated SOLR-7555:
Attachment: DiskSpaceAwareDirectory.java
SOLR-7555-display_disk_space_v3.patch
Here is a patc
Hello, just wondering, what would be the process for getting a patch that I
submitted few days ago reviewed and considered for one of the next releases?
The patch is this one: https://issues.apache.org/jira/browse/SOLR-7583. I've
submitted the last version about 4 days ago.
Thanks,
Greg
[
https://issues.apache.org/jira/browse/SOLR-7406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566301#comment-14566301
]
Gregg Donovan commented on SOLR-7406:
-
One minor bit - is the import of org.apache.log4
[
https://issues.apache.org/jira/browse/SOLR-7555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566295#comment-14566295
]
Eric Pugh commented on SOLR-7555:
-
Makes sense. I am working on another patch that based
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/862/
1 tests failed.
REGRESSION: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test
Error Message:
Error from server at https://127.0.0.1:54551: Error CREATEing SolrCore
'halfcollection_shard1_replica1': Unable to create
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/2365/
Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseG1GC
1 tests failed.
FAILED: org.apache.solr.search.TestSearcherReuse.test
Error Message:
expected same:
was not:
Stack Trace:
java.lang.AssertionError: expected same:
was
[
https://issues.apache.org/jira/browse/SOLR-7572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566211#comment-14566211
]
Vijay Sekhri commented on SOLR-7572:
Our suspicion here is that some default setting or
[
https://issues.apache.org/jira/browse/SOLR-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566209#comment-14566209
]
Vijay Sekhri commented on SOLR-5850:
One more observation here is if we increase the po
[
https://issues.apache.org/jira/browse/SOLR-7571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566206#comment-14566206
]
Vijay Sekhri commented on SOLR-7571:
Ideally if a system cannot handle a high rate, it
Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java8/28/
1 tests failed.
REGRESSION: org.apache.solr.cloud.BasicDistributedZkTest.test
Error Message:
commitWithin did not work on node: http://127.0.0.1:50861/collection1
expected:<68> but was:<67>
Stack Trace:
java.lang.AssertionE
Did this, out of curiosity (from a server in the U.S.):
# time git clone https://github.com/apache/lucene-solr.git
...
Receiving objects: 100% (563630/563630), 472.01 MiB | 10.46 MiB/s, done.
real1m13.049s
user0m46.000s
sys 0m10.060s
# time git clone --depth 1 https://github.com/apac
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/4749/
Java: 32bit/jdk1.8.0_45 -client -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.cloud.TestCloudPivotFacet.test
Error Message:
init query failed:
{main(facet=true&facet.pivot=%7B%21stats%3Dst1%7Dpivot_td%2Cpivot_
+1 to moving to git. I am not going to attempt to convince those stubborn types
that want to stick to SVN. I use git and svn and git simply works better for me.
I just want to explain something, because there seems to be a misunderstanding.
> time git clone git://git.apache.org/lucene-solr.git te
[
https://issues.apache.org/jira/browse/SOLR-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566096#comment-14566096
]
Xu Zhang commented on SOLR-7495:
Currently, I think Facet.field only works fine when the it
Steve Davids created SOLR-7613:
--
Summary: solrcore.properties file should be loaded if it resides
in ZooKeeper
Key: SOLR-7613
URL: https://issues.apache.org/jira/browse/SOLR-7613
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566084#comment-14566084
]
Ted Sullivan commented on SOLR-7539:
Added logic to handle the case where a phrase matc
[
https://issues.apache.org/jira/browse/SOLR-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Sullivan updated SOLR-7539:
---
Attachment: SOLR-7539.patch
> Add a QueryAutofilteringComponent for query introspection using indexed
On 5/30/2015 6:59 AM, Adrien Grand wrote:
> The main benefit I see is that external contributors would get their
> name in the commit log.
>
> However on the other hand, I'm a bit annoyed that people easily
> disagree on the workflow: some people merge into the maintenance
> branch first and then
[
https://issues.apache.org/jira/browse/SOLR-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566060#comment-14566060
]
Uwe Schindler edited comment on SOLR-7606 at 5/30/15 3:37 PM:
--
[
https://issues.apache.org/jira/browse/SOLR-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated SOLR-7606:
Attachment: LUCENE-6512.patch
Patch that moves to catching the index out of bounds as a "buest effort
[
https://issues.apache.org/jira/browse/SOLR-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566051#comment-14566051
]
Uwe Schindler commented on SOLR-7606:
-
Hi Yonik,
I agree. The problem is currently Solr
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/12883/
Java: 64bit/jdk1.9.0-ea-b60 -XX:-UseCompressedOops -XX:+UseG1GC
1 tests failed.
FAILED: org.apache.solr.cloud.CustomCollectionTest.test
Error Message:
Error from server at http://127.0.0.1:55010: collection already exists:
rou
[
https://issues.apache.org/jira/browse/SOLR-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566014#comment-14566014
]
Yonik Seeley commented on SOLR-7606:
Seems like Lucene's implementation is overly const
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/12707/
Java: 32bit/jdk1.8.0_60-ea-b12 -client -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.search.TestSearcherReuse.test
Error Message:
expected same: was
not:
Stack Trace:
java.lang.AssertionError: expected same: w
The main benefit I see is that external contributors would get their
name in the commit log.
However on the other hand, I'm a bit annoyed that people easily
disagree on the workflow: some people merge into the maintenance
branch first and then to master, other people merge into master first
and th
A git clone is just too slow right now the way its setup. So what will
be done to fix that? Currently, svn is way faster in the worst case.
In the time it takes to git clone, i can do 10 svn checkouts.
I sometimes use git, but usually when working on software, i don't
work on trivial things. I do
Ok, sounds good. I plan to finish up the page this weekend.
Joel Bernstein
http://joelsolr.blogspot.com/
On Fri, May 29, 2015 at 2:24 PM, Chris Hostetter
wrote:
>
> Joel: that table is pretty dense -- i would suggest instead using an
> subsection for each "Stream Function" with a table for the
bq. I don't think that moving to GIT has anything to do with Github.
I think that's a common misconception by people that don't 'get' Git. Most
people could care less about Git as it pertains to GitHub except for one
thing - it provides a nice central master repo that is hosted that you can
push t
The commit then push workflow *is* what allows you to maintain multiple
local branches without the nightmare of having multiple checkouts, and
managing them.
I don't think that moving to GIT has anything to do with Github. With SVN,
we also don't have any nice user interface and/or pull requests,
[
https://issues.apache.org/jira/browse/LUCENE-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565944#comment-14565944
]
Karl Wright commented on LUCENE-6487:
-
Ok, what I find is that because the arc distan
Ok, what I find is that because the arc distance is in effect taking a
square root, instead of 1e-12 the error should always be 1e-6. That is
just the way the math works.
Karl
Sent from my Windows Phone
From: Karl Wright (JIRA)
Sent: 5/30/2015 6:22 AM
To: dev@lucene.apache.org
Subject: [jira] [Co
[
https://issues.apache.org/jira/browse/LUCENE-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565926#comment-14565926
]
Karl Wright commented on LUCENE-6487:
-
I'll have a look. Please bear in mind that tr
Hi,
I think most people say that GIT is easier or better to use because they
combine in their mind using „GIT“ with „the Github user interface“.
This is indeed very nice to have - I (for myself) am also very happy with using
Github, as long as it keeps simple (you only have users from Git
As I've mentioned multiple times, I think git is super useful when working
on multiple unrelated things that affect the same files.
What I'd been doing so far with svn is, creating multiple physical
directories (checkouts) and working on them, and tracking them, cleaning
them up, and deleting them
Walter Underwood wrote:
> I’m not a committer, but I’ve built production code with a lot of source
> control
> systems and git is by far the the most cumbersome.
I am not a committer and I have build production code with very few source
control systems: CVS, SVN & GIT. GIT is the one I dislike
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/2362/
Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.schema.TestCloudSchemaless.test
Error Message:
QUERY FAILED:
xpath=/response/arr[@name='fields']/lst/str[@name='name']
[
https://issues.apache.org/jira/browse/LUCENE-6508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565870#comment-14565870
]
ASF subversion and git services commented on LUCENE-6508:
-
Commit
45 matches
Mail list logo
