[
https://issues.apache.org/jira/browse/SOLR-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360001#comment-14360001
]
Hoss Man commented on SOLR-7240:
bq. ... what API is the root url going to service during s
[
https://issues.apache.org/jira/browse/SOLR-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359939#comment-14359939
]
abhishek bafna commented on SOLR-7193:
--
[~jmtd890917] Did you get the point I tried to
[
https://issues.apache.org/jira/browse/SOLR-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359890#comment-14359890
]
Erick Erickson commented on SOLR-2366:
--
I don't think this ever got committed, but the
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/4435/
Java: 32bit/jdk1.7.0_76 -client -XX:+UseSerialGC
1 tests failed.
FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test
Error Message:
Captured an uncaught exception in thread: Thread[id=11219, name=collection1,
sta
That explains a lot. Thanks Mike!
On 13 Mar 2015 00:46, "Michael McCandless"
wrote:
> On Thu, Mar 12, 2015 at 5:38 PM, Yonik Seeley wrote:
> > On Thu, Mar 12, 2015 at 8:04 PM, Ramkumar R. Aiyengar
> > wrote:
> >> This actually brings me to a question I have had for a while. Why do we
> >> check
On 12 March 2015 at 21:43, Kitty wrote:
> I did some further digging in the long test output log. There are no error
> messages, actually it says:
>
> The following error occurred while executing this line:
>
> And then nothing following that. Empty line.
Don't know about the actual suits that ar
Thank you! :)
I already hit the missing ivy and followed instructions to fix it, so that
passed.
I did some further digging in the long test output log. There are no error
messages, actually it says:
The following error occurred while executing this line:
And then nothing following that. Emp
Welcome.
Right list, strange problem, what's the actual error? Could be related
to missing ivy, but the specific message will help.
Regards,
Alex.
Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
http://www.solr-start.com/
On 12 March 2015 at 21:30, Kitty wrote:
> Hi a
[
https://issues.apache.org/jira/browse/SOLR-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359751#comment-14359751
]
Alexandre Rafalovitch commented on SOLR-6892:
-
We better have the debugging sta
Hi all,
I'm not entirely sure this is not a user question, but it is a newbie question
from a dev perspective still, so not sure if it belongs here on the dev list or
not... I am open to coaching in that case on where to go with this question.
I am very new to the experience of contributing to o
Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2761/
3 tests failed.
FAILED: org.apache.solr.cloud.LeaderInitiatedRecoveryOnCommitTest.test
Error Message:
IOException occured when talking to server at:
http://127.0.0.1:64839/c8n_1x3_commits_shard1_replica3
Stack Trace:
org.ap
On Thu, Mar 12, 2015 at 5:38 PM, Yonik Seeley wrote:
> On Thu, Mar 12, 2015 at 8:04 PM, Ramkumar R. Aiyengar
> wrote:
>> This actually brings me to a question I have had for a while. Why do we
>> check in auto generated code? Shouldn't the build system run javacc as a
>> prereq to compiling inste
On Thu, Mar 12, 2015 at 8:04 PM, Ramkumar R. Aiyengar
wrote:
> This actually brings me to a question I have had for a while. Why do we
> check in auto generated code? Shouldn't the build system run javacc as a
> prereq to compiling instead?
Historically, the compilation wasn't automated (you had
[
https://issues.apache.org/jira/browse/SOLR-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359691#comment-14359691
]
Ramkumar Aiyengar commented on SOLR-7240:
-
Re: your comment on having /solr so that
[
https://issues.apache.org/jira/browse/SOLR-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandre Rafalovitch closed SOLR-5994.
---
Resolution: Won't Fix
Fix Version/s: (was: Trunk)
No longer relevant.
> Add
[
https://issues.apache.org/jira/browse/SOLR-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359682#comment-14359682
]
Alexandre Rafalovitch commented on SOLR-5994:
-
I think this issue is dead with
This actually brings me to a question I have had for a while. Why do we
check in auto generated code? Shouldn't the build system run javacc as a
prereq to compiling instead?
On 12 Mar 2015 18:08, "Alan Woodward" wrote:
> Ah, OK. Sorry for the noise!
>
> On 12 Mar 2015, at 15:19, Yonik Seeley wro
[
https://issues.apache.org/jira/browse/SOLR-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359648#comment-14359648
]
Hoss Man commented on SOLR-7240:
Hmm, not sure i'm a fan of this solution actually...
it o
[
https://issues.apache.org/jira/browse/SOLR-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-7240:
---
Attachment: SOLR-7240.patch
patch leveraging a bit of jetty magic to do this.
> redirect / to /solr
> ---
[
https://issues.apache.org/jira/browse/SOLR-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359635#comment-14359635
]
Hoss Man commented on SOLR-7240:
In response to the inevitable question "why not just move
Hoss Man created SOLR-7240:
--
Summary: redirect / to /solr
Key: SOLR-7240
URL: https://issues.apache.org/jira/browse/SOLR-7240
Project: Solr
Issue Type: Improvement
Reporter: Hoss Man
[
https://issues.apache.org/jira/browse/SOLR-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359562#comment-14359562
]
Jacob Carter commented on SOLR-5743:
I've applied this patch to the Solr 5.0.0 and with
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/11967/
Java: 64bit/jdk1.8.0_31 -XX:-UseCompressedOops -XX:+UseG1GC
1 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeyNothingIsSafeTest.test
Error Message:
There were too many update fails - we expect it can happen, but shouldn'
[
https://issues.apache.org/jira/browse/SOLR-7239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-7239.
Resolution: Fixed
Fix Version/s: 5.1
Trunk
> StatsComponent perf improvement for mi
[
https://issues.apache.org/jira/browse/SOLR-7239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359436#comment-14359436
]
ASF subversion and git services commented on SOLR-7239:
---
Commit 16663
Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2760/
5 tests failed.
FAILED: org.apache.solr.cloud.HttpPartitionTest.test
Error Message:
org.apache.http.NoHttpResponseException: The target server failed to respond
Stack Trace:
org.apache.solr.client.solrj.SolrServerException:
[
https://issues.apache.org/jira/browse/SOLR-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter resolved SOLR-7173.
--
Resolution: Fixed
> Fix ReplicationFactorTest on Windows
>
>
[
https://issues.apache.org/jira/browse/SOLR-7239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359353#comment-14359353
]
ASF subversion and git services commented on SOLR-7239:
---
Commit 16662
[
https://issues.apache.org/jira/browse/SOLR-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359331#comment-14359331
]
ASF subversion and git services commented on SOLR-7173:
---
Commit 16662
[
https://issues.apache.org/jira/browse/SOLR-7231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359214#comment-14359214
]
Tim Allison edited comment on SOLR-7231 at 3/12/15 7:37 PM:
Pat
[
https://issues.apache.org/jira/browse/SOLR-7215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359227#comment-14359227
]
Dawid Weiss commented on SOLR-7215:
---
Uncomment the ThreadLeakFilters, Hoss. Nothing shoul
[
https://issues.apache.org/jira/browse/SOLR-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey closed SOLR-7234.
--
Assignee: (was: Steve Rowe)
I believe that the problem here is that the user changed the schemaFactor
[
https://issues.apache.org/jira/browse/SOLR-7231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated SOLR-7231:
--
Attachment: test_jpeg.jpg
SOLR-7231.patch
Patch attached. Borrowed heavily from SpatialF
[
https://issues.apache.org/jira/browse/SOLR-7239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-7239:
---
Attachment: SOLR-7324.patch
this patch optimizes away the "none" stat case, as well as caches the min/max
nume
Hoss Man created SOLR-7239:
--
Summary: StatsComponent perf improvement for min, max, and
situations where all stats disabled
Key: SOLR-7239
URL: https://issues.apache.org/jira/browse/SOLR-7239
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359161#comment-14359161
]
Yonik Seeley commented on SOLR-7238:
The current Solr uses are all in BlobHandler.
The
Yonik Seeley created SOLR-7238:
--
Summary: SolrQueryRequest.forward is buggy
Key: SOLR-7238
URL: https://issues.apache.org/jira/browse/SOLR-7238
Project: Solr
Issue Type: Bug
Affects Versions
[
https://issues.apache.org/jira/browse/SOLR-7215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-7215:
---
Summary: non reproducible Suite failures due to excessive sysout due to
HDFS lease renewal WARN logs due to con
[
https://issues.apache.org/jira/browse/SOLR-7215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359123#comment-14359123
]
Hoss Man commented on SOLR-7215:
This is more jacked up then i thought -- i just got one of
Ah, OK. Sorry for the noise!
On 12 Mar 2015, at 15:19, Yonik Seeley wrote:
> On Thu, Mar 12, 2015 at 11:08 AM, Alan Woodward wrote:
>> Hey Yonik,
>>
>> I think you've inadvertently added a couple of deprecated methods back in
>> here?
>
> Hmmm, but CharStream.java is generated by JavaCC...
>
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/2051/
Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
4 tests failed.
FAILED: org.apache.solr.cloud.LeaderFailoverAfterPartitionTest.test
Error Message:
Didn't see replicas [core_node2, core_node3] come up within
[
https://issues.apache.org/jira/browse/SOLR-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359084#comment-14359084
]
Timothy Potter commented on SOLR-7173:
--
thanks [~ichattopadhyaya]!
> Fix ReplicationF
[
https://issues.apache.org/jira/browse/SOLR-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter reassigned SOLR-7173:
Assignee: Timothy Potter
> Fix ReplicationFactorTest on Windows
> --
[
https://issues.apache.org/jira/browse/SOLR-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359081#comment-14359081
]
ASF subversion and git services commented on SOLR-7173:
---
Commit 16662
Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2759/
5 tests failed.
FAILED: org.apache.solr.cloud.HttpPartitionTest.test
Error Message:
org.apache.solr.client.solrj.SolrServerException: IOException occured when
talking to server at: http://127.0.0.1:56926/c8n_1x2_shard1_repli
[
https://issues.apache.org/jira/browse/SOLR-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359029#comment-14359029
]
Yonik Seeley commented on SOLR-6787:
bq. what is the solution?
I'm pointing out the p
bq. how is copying a core dir from one node to another a normal use case ?
That was just for testing what happens.
Okay here is a real world scenario -
- I create a collection.
- The collection fails to create since it had a bad config. The empty
folders for the replicas gets left behin
[
https://issues.apache.org/jira/browse/SOLR-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358957#comment-14358957
]
Luc Vanlerberghe commented on SOLR-6070:
I also tried using different highlighters
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/784/
8 tests failed.
REGRESSION: org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.test
Error Message:
shard3 is not consistent. Got 110 from
http://127.0.0.1:59031/collection1lastClient and got 47 from
http://127.0.0.1:59057/col
bq.Or they're testing out restoring backups
This is in the context of ZK as truth functionality. I guess , in that case
you expect those nodes to work exactly as the other replica
On Thu, Mar 12, 2015 at 8:36 PM, Erick Erickson
wrote:
> bq: how is copying a core dir from one node to another a n
Looks like the original removal of these deprecated methods happened
in SOLR-6976, but probably should not have given that this is a
generated file?
-Yonik
On Thu, Mar 12, 2015 at 11:19 AM, Yonik Seeley wrote:
> On Thu, Mar 12, 2015 at 11:08 AM, Alan Woodward wrote:
>> Hey Yonik,
>>
>> I think
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/4434/
Java: 32bit/jdk1.7.0_76 -server -XX:+UseG1GC
1 tests failed.
FAILED: org.apache.solr.cloud.ReplicationFactorTest.test
Error Message:
org.apache.solr.client.solrj.SolrServerException: IOException occured when
talking to server a
On Thu, Mar 12, 2015 at 11:08 AM, Alan Woodward wrote:
> Hey Yonik,
>
> I think you've inadvertently added a couple of deprecated methods back in
> here?
Hmmm, but CharStream.java is generated by JavaCC...
When I got a compile error in FastCharStream.java, I simply copied the
lucene version.
I
bq: how is copying a core dir from one node to another a normal use case ?
A user is trying to move a replica from one place to another. While I
agree they should use ADDREPLICA for the new one then DELTERPLICA on
the old replica..
Or they're testing out restoring backups.
I've had clients do bo
Hey Yonik,
I think you've inadvertently added a couple of deprecated methods back in here?
>
> Modified:
> lucene/dev/branches/branch_5x/solr/core/src/java/org/apache/solr/parser/CharStream.java
> URL:
> http://svn.apache.org/viewvc/lucene/dev/branches/branch_5x/solr/core/src/java/org/apache/s
[
https://issues.apache.org/jira/browse/SOLR-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358720#comment-14358720
]
Noble Paul commented on SOLR-6787:
--
bq. don't use a response object after the request has
how is copying a core dir from one node to another a normal use case ?
On Mar 12, 2015 7:22 PM, "Varun Thacker" wrote:
> Hi Noble,
>
> Well I was just playing around to see if there were scenarios where
> different coreNodeNames could register themselves even if they weren't
> creating using the
[
https://issues.apache.org/jira/browse/SOLR-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358693#comment-14358693
]
Yonik Seeley commented on SOLR-6787:
Even with a different handler though... "forwardin
[
https://issues.apache.org/jira/browse/LUCENE-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-6347.
Resolution: Duplicate
I dug into this, saw it wouldn't repro on 4.10.x but would on
Hi Noble,
Well I was just playing around to see if there were scenarios where
different coreNodeNames could register themselves even if they weren't
creating using the Collections API.
So I was doing it intentionally here to see what happens. But I can totally
imagine users running into the secon
[
https://issues.apache.org/jira/browse/SOLR-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358685#comment-14358685
]
Shawn Heisey commented on SOLR-7191:
[~dk]:
The first thing I thought when I saw that
The DELETE and PUT formats are going to be deprecated in favor of the bulk
APIs
Please take a look at the ref guide
https://cwiki.apache.org/confluence/display/solr/Schema+API
On Thu, Mar 12, 2015 at 9:32 AM, Dourm wrote:
> Github user Dourm commented on the pull request:
>
> https://github
[
https://issues.apache.org/jira/browse/SOLR-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358674#comment-14358674
]
Yonik Seeley commented on SOLR-7217:
I haven't created a patch yet... it was part of a
[
https://issues.apache.org/jira/browse/SOLR-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358673#comment-14358673
]
Noble Paul commented on SOLR-6787:
--
I agree with you that recursive screw up is possible.
[
https://issues.apache.org/jira/browse/LUCENE-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358669#comment-14358669
]
Michael McCandless commented on LUCENE-6347:
Thanks Paul, indeed, now I can s
[
https://issues.apache.org/jira/browse/SOLR-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358665#comment-14358665
]
Noble Paul commented on SOLR-7237:
--
It is possible, But, but it is not enough if consideri
[
https://issues.apache.org/jira/browse/SOLR-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-7218.
Resolution: Fixed
Fix Version/s: 5.1
Trunk
> constant score query syntax
>
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/4543/
Java: 32bit/jdk1.8.0_31 -server -XX:+UseSerialGC
2 tests failed.
FAILED: org.apache.solr.TestDistributedSearch.test
Error Message:
Error from server at http://127.0.0.1:56034//collection1:
java.lang.NullPointerException at
It is totally possible.
The point is , it was not a security feature and it is extremely easy to
spoof it.
The question is , was it a normal scenario or was it an effort to prove
that the system was not foolproof
--Noble
On Thu, Mar 12, 2015 at 6:23 PM, Varun Thacker
wrote:
> Two scenarios I ob
[
https://issues.apache.org/jira/browse/SOLR-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358659#comment-14358659
]
ASF subversion and git services commented on SOLR-7218:
---
Commit 16661
[
https://issues.apache.org/jira/browse/SOLR-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358656#comment-14358656
]
ASF subversion and git services commented on SOLR-7218:
---
Commit 16661
[
https://issues.apache.org/jira/browse/SOLR-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358650#comment-14358650
]
Uwe Schindler commented on SOLR-7217:
-
Hi, where is a patch or commit link in Heliosear
[
https://issues.apache.org/jira/browse/SOLR-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358638#comment-14358638
]
Yonik Seeley commented on SOLR-6787:
bq. The problem I see with our internal APIs is th
[
https://issues.apache.org/jira/browse/SOLR-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358634#comment-14358634
]
Noble Paul commented on SOLR-7217:
--
Good , I overlooked it. I was trying to cleanup our ex
[
https://issues.apache.org/jira/browse/LUCENE-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-6357.
Resolution: Duplicate
OK this is a dup of LUCENE-6084, where we added a required "S
[
https://issues.apache.org/jira/browse/SOLR-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-6892:
-
Attachment: SOLR-6892.patch
> Improve the way update processors are used and make it simpler
>
Karl Kildén created SOLR-7237:
-
Summary: Add boost to @Field annotation
Key: SOLR-7237
URL: https://issues.apache.org/jira/browse/SOLR-7237
Project: Solr
Issue Type: Improvement
Compone
Two scenarios I observed where we can bring up a replica even when I think
it shouldn't. legacyCloud is set to false.
- I have two nodes A and B.
- CREATE collection 'test' with 1 shard, 1 replica. It gets created on
node A.
- manually copy test_shard1_replica1 folder to node B's solr
Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2758/
1 tests failed.
REGRESSION:
org.apache.lucene.analysis.core.TestRandomChains.testRandomChainsWithLargeStrings
Error Message:
some thread(s) failed
Stack Trace:
java.lang.RuntimeException: some thread(s) failed
at
o
[
https://issues.apache.org/jira/browse/SOLR-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358587#comment-14358587
]
Yonik Seeley commented on SOLR-7217:
bq. But how do we know that client is curl? does i
[
https://issues.apache.org/jira/browse/SOLR-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358581#comment-14358581
]
Noble Paul commented on SOLR-7217:
--
But how do we know that client is curl? does it send a
Hi Mark,
On Wednesday, March 11, 2015, wrote:
> +## Releases:
> +
> + - 5.0 was released on Fri Feb 20 2015
> + - 4.10.3 was released on Mon Dec 29 2014
4.10.4 is missing - maybe its metadata is missing from a doap file or
something?
> + PyLucene
> +
[...]
> +
> +No releases where
[
https://issues.apache.org/jira/browse/SOLR-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358547#comment-14358547
]
Yonik Seeley commented on SOLR-7217:
If anyone wants to try it out in practice before i
[
https://issues.apache.org/jira/browse/SOLR-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358546#comment-14358546
]
Yonik Seeley commented on SOLR-7217:
If the client is curl AND the content-type is curl
[
https://issues.apache.org/jira/browse/SOLR-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358527#comment-14358527
]
Noble Paul commented on SOLR-7217:
--
I didn't get that. what does the server do if content
[
https://issues.apache.org/jira/browse/SOLR-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358486#comment-14358486
]
Yonik Seeley edited comment on SOLR-7217 at 3/12/15 11:03 AM:
--
[
https://issues.apache.org/jira/browse/SOLR-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358486#comment-14358486
]
Yonik Seeley commented on SOLR-7217:
Right, so the logic is to autodetect if there is n
[
https://issues.apache.org/jira/browse/LUCENE-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358440#comment-14358440
]
Paul taylor commented on LUCENE-6347:
-
Hm, Ive just retested it and with assertions e
[
https://issues.apache.org/jira/browse/SOLR-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358401#comment-14358401
]
Jan Høydahl edited comment on SOLR-7236 at 3/12/15 9:58 AM:
Var
[
https://issues.apache.org/jira/browse/SOLR-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358401#comment-14358401
]
Jan Høydahl commented on SOLR-7236:
---
There are multiple existing frameworks to simplify t
[
https://issues.apache.org/jira/browse/LUCENE-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated LUCENE-6332:
-
Attachment: LUCENE-6332.patch
attaching DocValuesScanQuery.java with a trivial test. It w
[
https://issues.apache.org/jira/browse/SOLR-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358382#comment-14358382
]
Jan Høydahl commented on SOLR-7230:
---
Created SOLR-7236 as an umbrella.
> An API to plugi
Jan Høydahl created SOLR-7236:
-
Summary: Securing Solr (umbrella issue)
Key: SOLR-7236
URL: https://issues.apache.org/jira/browse/SOLR-7236
Project: Solr
Issue Type: New Feature
Repor
[
https://issues.apache.org/jira/browse/SOLR-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358367#comment-14358367
]
Noble Paul commented on SOLR-7230:
--
bq.This issue lacks a lot of context and high level en
Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2757/
5 tests failed.
FAILED: org.apache.solr.cloud.HttpPartitionTest.test
Error Message:
org.apache.solr.client.solrj.SolrServerException: IOException occured when
talking to server at: http://127.0.0.1:61014/c8n_1x2_shard1_repli
[
https://issues.apache.org/jira/browse/SOLR-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358348#comment-14358348
]
Jan Høydahl commented on SOLR-7230:
---
This issue lacks a lot of context and high level end
[
https://issues.apache.org/jira/browse/LUCENE-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14356998#comment-14356998
]
Paul taylor commented on LUCENE-6347:
-
It only shows the NPE when you run the query,
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/2050/
Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseSerialGC
1 tests failed.
FAILED: org.apache.solr.core.TestDynamicLoading.testDynamicLoading
Error Message:
Could not get expected value 'org.apache.solr.core.RuntimeLibReqHan
i realize this question has been asked in the past (sept-2013) but the
answer seems to be less than useful.
i'm using JCC via C++ and having java crashing issues. the problem appears
to be with the use of initializeClass(bool) and storing instances of JCC
objects.
first off, what does initializeC
[
https://issues.apache.org/jira/browse/SOLR-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14356812#comment-14356812
]
Tim Allison edited comment on SOLR-7229 at 3/11/15 5:30 PM:
Y,
1 - 100 of 103 matches
Mail list logo