Simon Willnauer created LUCENE-4961:
---
Summary: Filters should return null if they don't accept documents
Key: LUCENE-4961
URL: https://issues.apache.org/jira/browse/LUCENE-4961
Project: Lucene -
[
https://issues.apache.org/jira/browse/LUCENE-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-4961:
Attachment: LUCENE-4961.patch
here is a first patch
Filters should
can someone from solr land comment on the SLF4j issue? I am not sure I
can make a decision if that should block a release.
thanks,
simon
On Thu, Apr 25, 2013 at 11:07 PM, Ryan Ernst r...@iernst.net wrote:
-1
It seems SLF4j packaging is busted? I thought I remembered slf4j jars were
removed
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-trunk/246/
1 tests failed.
FAILED: org.apache.lucene.search.join.TestBlockJoinSorting.testNestedSorting
Error Message:
expected:3 but was:15
Stack Trace:
java.lang.AssertionError: expected:3 but was:15
at
I'm looking into this failure.
On 26 April 2013 12:01, Apache Jenkins Server jenk...@builds.apache.orgwrote:
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-trunk/246/
1 tests failed.
FAILED:
org.apache.lucene.search.join.TestBlockJoinSorting.testNestedSorting
Error
[
https://issues.apache.org/jira/browse/LUCENE-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642735#comment-13642735
]
Michael McCandless commented on LUCENE-4961:
+1
Filters
[
https://issues.apache.org/jira/browse/LUCENE-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642737#comment-13642737
]
Michael McCandless commented on LUCENE-4957:
+1
Stop
Thomas Romera created SOLR-4767:
---
Summary: Geofilt is not accurate
Key: SOLR-4767
URL: https://issues.apache.org/jira/browse/SOLR-4767
Project: Solr
Issue Type: Bug
Components:
i dont understand logging at all... needing 6 or 7 jars to
System.out.println is the most ridiculous thing in the world to me. So
someone else will have to comment about which one is right, the .tgz or
maven
but it seems totally broken for the war to have a bunch of extra jars in
maven that it
[
https://issues.apache.org/jira/browse/LUCENE-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642744#comment-13642744
]
Commit Tag Bot commented on LUCENE-4955:
[trunk commit] jpountz
On Fri, Apr 26, 2013 at 6:57 AM, Robert Muir rcm...@gmail.com wrote:
i dont understand logging at all... needing 6 or 7 jars to
System.out.println is the most ridiculous thing in the world to me. So
someone else will have to comment about which one is right, the .tgz or
maven
but it
On Fri, Apr 26, 2013 at 7:06 AM, Michael McCandless
luc...@mikemccandless.com wrote:
On Fri, Apr 26, 2013 at 6:57 AM, Robert Muir rcm...@gmail.com wrote:
i dont understand logging at all... needing 6 or 7 jars to
System.out.println is the most ridiculous thing in the world to me. So
On Fri, Apr 26, 2013 at 7:34 AM, Robert Muir rcm...@gmail.com wrote:
I would try to help fix it: but its not clear to me which 'package' is
correct or what happened to logging at all in 4.3
Solr's CHANGES has a summary:
* Slf4j/logging jars are no longer included in the Solr webapp. All
[
https://issues.apache.org/jira/browse/LUCENE-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642762#comment-13642762
]
Michael McCandless commented on LUCENE-4953:
I feel like we are making the
On Fri, Apr 26, 2013 at 7:50 AM, Yonik Seeley yo...@lucidworks.com wrote:
On Fri, Apr 26, 2013 at 7:34 AM, Robert Muir rcm...@gmail.com wrote:
I would try to help fix it: but its not clear to me which 'package' is
correct or what happened to logging at all in 4.3
Solr's CHANGES has a
I really love how you can reply without telling if we still have a
problem or not :D
simon
On Fri, Apr 26, 2013 at 1:50 PM, Yonik Seeley yo...@lucidworks.com wrote:
On Fri, Apr 26, 2013 at 7:34 AM, Robert Muir rcm...@gmail.com wrote:
I would try to help fix it: but its not clear to me which
[
https://issues.apache.org/jira/browse/SOLR-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642767#comment-13642767
]
Commit Tag Bot commented on SOLR-4766:
--
[branch_4x commit] mikemccand
[
https://issues.apache.org/jira/browse/SOLR-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642768#comment-13642768
]
Commit Tag Bot commented on SOLR-4766:
--
[trunk commit] mikemccand
[
https://issues.apache.org/jira/browse/SOLR-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642769#comment-13642769
]
Michael McCandless commented on SOLR-4766:
--
I committed a fix that seems to catch
[
https://issues.apache.org/jira/browse/SOLR-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642770#comment-13642770
]
Robert Muir commented on SOLR-4766:
---
Thank you Mike!
smoketester to
[
https://issues.apache.org/jira/browse/SOLR-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved SOLR-4766.
--
Resolution: Fixed
Fix Version/s: (was: 4.3)
4.4
[
https://issues.apache.org/jira/browse/LUCENE-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642772#comment-13642772
]
Commit Tag Bot commented on LUCENE-4955:
[branch_4x commit] jpountz
It's a Maven problem as far as I'm concerned, and committers don't need to
worry about Maven last we discussed, just the ones interested in Maven. So
unless a Maven guy wants to address this, I'd say we are good to go!
I'd prefer Maven was downstream myself ;)
Everything else is as expected.
[
https://issues.apache.org/jira/browse/LUCENE-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642839#comment-13642839
]
Commit Tag Bot commented on LUCENE-4961:
[trunk commit] simonw
[
https://issues.apache.org/jira/browse/SOLR-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642821#comment-13642821
]
Steve Rowe commented on SOLR-4766:
--
bq. I committed a fix that seems to catch the current
On Fri, Apr 26, 2013 at 7:55 AM, Simon Willnauer
simon.willna...@gmail.com wrote:
I really love how you can reply without telling if we still have a
problem or not :D
I was responding to the what happened to logging at all in 4.3.
As to which WAR is correct, it's answered in the *first
[
https://issues.apache.org/jira/browse/SOLR-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642841#comment-13642841
]
Robert Muir commented on SOLR-4766:
---
Maybe we can just compare filenames for now? Its an
On Fri, Apr 26, 2013 at 9:34 AM, Yonik Seeley yo...@lucidworks.com wrote:
On Fri, Apr 26, 2013 at 7:55 AM, Simon Willnauer
simon.willna...@gmail.com wrote:
I really love how you can reply without telling if we still have a
problem or not :D
I was responding to the what happened to logging
[
https://issues.apache.org/jira/browse/SOLR-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642849#comment-13642849
]
Steve Rowe commented on SOLR-4766:
--
bq. I think filesizes are unsafe at the moment, too.
On Apr 26, 2013, at 9:36 AM, Robert Muir rcm...@gmail.com wrote:
In my opinion shipping a war that does not actually work is broken, because
its really no war at all.
We don't ship a war, we ship Solr. To use our war outside of what we ship,
setup the logging as CHANGES says to do. It's
On Fri, Apr 26, 2013 at 9:36 AM, Robert Muir rcm...@gmail.com wrote:
On Fri, Apr 26, 2013 at 9:34 AM, Yonik Seeley yo...@lucidworks.com wrote:
As to which WAR is correct, it's answered in the *first sentence* of
what I quoted:
Slf4j/logging jars are no longer included in the Solr webapp
[
https://issues.apache.org/jira/browse/SOLR-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642854#comment-13642854
]
Robert Muir commented on SOLR-4766:
---
Yeah im just trying to figure out if its safe in
[
https://issues.apache.org/jira/browse/SOLR-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642855#comment-13642855
]
Robert Muir commented on SOLR-4766:
---
yeah i think thats the issue. I think with the
[
https://issues.apache.org/jira/browse/LUCENE-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642868#comment-13642868
]
Commit Tag Bot commented on LUCENE-4961:
[branch_4x commit] simonw
[
https://issues.apache.org/jira/browse/LUCENE-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-4961.
-
Resolution: Fixed
Assignee: Simon Willnauer
Filters should return null if
I know why the two .wars are different:
The binary package Solr war's target chain is:
'package'-'create-package'-'dist'-'dist-war'-webapp:'dist'
The maven Solr war's target chain is:
'generate-maven-artifacts'-webapp:'dist-maven'-webapp:'dist'
So both create the war using
I am taking it up with them. Right now before its ever released. I don't
think our pmc should release two different solr-4.3.0.war files at
different download locations. And I think the war we do release, should
work.
On Apr 26, 2013 10:06 AM, Yonik Seeley yo...@lucidworks.com wrote:
On Fri, Apr
Steve Rowe created SOLR-4768:
Summary: The Solr war produced by generate-maven-artifacts should
not contain logging jars
Key: SOLR-4768
URL: https://issues.apache.org/jira/browse/SOLR-4768
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-4768:
-
Description:
I know why the two .wars are different:
The binary package Solr war's target chain is:
[
https://issues.apache.org/jira/browse/LUCENE-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642885#comment-13642885
]
Uwe Schindler commented on LUCENE-4953:
---
bq. I feel like we are making the wrong
[
https://issues.apache.org/jira/browse/SOLR-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642892#comment-13642892
]
Steve Rowe commented on SOLR-4768:
--
Here's the patch:
{code:java}
Index: solr/build.xml
[
https://issues.apache.org/jira/browse/SOLR-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642893#comment-13642893
]
Commit Tag Bot commented on SOLR-4757:
--
[trunk commit] markrmiller
[
https://issues.apache.org/jira/browse/LUCENE-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand resolved LUCENE-4955.
--
Resolution: Fixed
NGramTokenFilter increments positions for each gram
[
https://issues.apache.org/jira/browse/LUCENE-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand reassigned LUCENE-4955:
Assignee: Adrien Grand
NGramTokenFilter increments positions for each gram
[
https://issues.apache.org/jira/browse/LUCENE-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand resolved LUCENE-3920.
--
Resolution: Fixed
Assignee: Adrien Grand
Fixed by LUCENE-4955.
ngram
[
https://issues.apache.org/jira/browse/LUCENE-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4953:
--
Attachment: LUCENE-4953.patch
Here an updated patch. The naming inside the enum was made with
[
https://issues.apache.org/jira/browse/SOLR-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642892#comment-13642892
]
Steve Rowe edited comment on SOLR-4768 at 4/26/13 2:39 PM:
---
[
https://issues.apache.org/jira/browse/SOLR-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642911#comment-13642911
]
Commit Tag Bot commented on SOLR-4757:
--
[branch_4x commit] markrmiller
[
https://issues.apache.org/jira/browse/SOLR-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-4757.
---
Resolution: Fixed
I'm sure there is more to shake out here, but that's part of why I'm making
this
[
https://issues.apache.org/jira/browse/SOLR-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-4758:
--
Issue Type: Test (was: Bug)
Zk bootstrapping does not work with the new solr.xml format and core
[
https://issues.apache.org/jira/browse/SOLR-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-4758.
---
Resolution: Fixed
Zk bootstrapping does not work with the new solr.xml format and core
Have to agree with the not distributing 2 wars. But externalizing the logging
jars is a great improvement for people integrating it. Repackaging the war to
change logging framework to fit the rest of your code is far from being the
best option. Adding the proper slf4j jars in your container’s
[
https://issues.apache.org/jira/browse/SOLR-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642914#comment-13642914
]
Steve Rowe commented on SOLR-4768:
--
With the above patch applied I ran {{ant
[
https://issues.apache.org/jira/browse/SOLR-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642917#comment-13642917
]
Commit Tag Bot commented on SOLR-4768:
--
[trunk commit] sarowe
[
https://issues.apache.org/jira/browse/LUCENE-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642918#comment-13642918
]
Kevin Lawson commented on LUCENE-4947:
--
bq. Kevin Lawson, did you send the code
[
https://issues.apache.org/jira/browse/SOLR-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642922#comment-13642922
]
Commit Tag Bot commented on SOLR-4768:
--
[branch_4x commit] sarowe
My problem is users will put the war in their container and get
ClassNotFoundExceptions.
Instead they should get some basic system.out.println-logger or some no-op
implementation.
6 or 7 logging jars in our distribution and you are telling me it cant do
simple stuff like this? What is the point
[
https://issues.apache.org/jira/browse/SOLR-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-4756.
---
Resolution: Fixed
Between my changes here and SOLR-4757, we now have a handful of important tests
[
https://issues.apache.org/jira/browse/LUCENE-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642929#comment-13642929
]
Uwe Schindler commented on LUCENE-4961:
---
Thanks! :-) Nice patch!
Another idea: We should maybe change the ClassNotFoundException to something
that makes a useful message:
If you did not put a logging implementation outside into your servlet
container’s lib dir, then solr should fail to start and throw a usefull
Exception. Ideally this could be done on
That actually makes a lot of sense. ☺
Steve Molloy
Software Architect | Information Discovery Analytics RD
[http://www.opentext.com/2/emailsupport-logo-opentext-2010.gif]http://www.opentext.com/2/email-signature-logo
This email message is confidential, may be privileged, and is intended for
[
https://issues.apache.org/jira/browse/SOLR-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642942#comment-13642942
]
Mark Miller commented on SOLR-4768:
---
Thanks Steve.
The Solr war
+1 - if we can manage a more useful message, that would be a good improvement.
bq. and SolrDispatchFilter should get the highest priority in web.xml, so its
loaded first.
The problem is, we don't really control that - especially in the case when
someone is just trying to suck up the war.
-
[
https://issues.apache.org/jira/browse/LUCENE-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642945#comment-13642945
]
Steve Rowe commented on LUCENE-4947:
bq. Ah, I definitely overlooked that. Sent! Was
Yeah. I want to catch the common case. Somebody downloads the war from Maven
and deploys it in his Tomcat. In that case the message should be displayed on
SolrDispatchFilter startup. If the other servlets in Solr don’t use a logging
impl, we are fine... Otherwise we can make some class
Unfortunately thats not possible with SFL4J: The „simplicity” of this framework
is based on the fact that the class path can only conatin *one* logging
implementation. If we ship with one we are back at the problem that users had
before, the one from the WAR file took preference.
The idea
[
https://issues.apache.org/jira/browse/SOLR-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642960#comment-13642960
]
Mark Miller commented on SOLR-4655:
---
Any progress with this @anshumg ?
[
https://issues.apache.org/jira/browse/SOLR-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642960#comment-13642960
]
Mark Miller edited comment on SOLR-4655 at 4/26/13 3:35 PM:
Any
[
https://issues.apache.org/jira/browse/SOLR-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642969#comment-13642969
]
Alan Woodward commented on SOLR-4735:
-
That's a nice idea. The MetricsReporters would
[
https://issues.apache.org/jira/browse/LUCENE-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642971#comment-13642971
]
Han Jiang commented on LUCENE-3069:
---
This is my inital proposal for this project:
[
https://issues.apache.org/jira/browse/LUCENE-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643001#comment-13643001
]
Kevin Lawson commented on LUCENE-4947:
--
The address I sent it to is indeed correct
[
https://issues.apache.org/jira/browse/SOLR-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643002#comment-13643002
]
philip hoy commented on SOLR-4448:
--
I don't know if anyone has had a chance to take a look
Mark Bennett created SOLR-4769:
--
Summary: Highlight Current Node in SolrCloud graphical display
Key: SOLR-4769
URL: https://issues.apache.org/jira/browse/SOLR-4769
Project: Solr
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SOLR-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bennett updated SOLR-4769:
---
Affects Version/s: 4.2
Highlight Current Node in SolrCloud graphical display
Mark Bennett created SOLR-4770:
--
Summary: Mouse-over info for other nodes in SolrCloud rendering
Key: SOLR-4770
URL: https://issues.apache.org/jira/browse/SOLR-4770
Project: Solr
Issue Type:
[
https://issues.apache.org/jira/browse/LUCENE-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643033#comment-13643033
]
Michael McCandless commented on LUCENE-4953:
To fix the first bug, I would
[
https://issues.apache.org/jira/browse/SOLR-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643055#comment-13643055
]
Commit Tag Bot commented on SOLR-4705:
--
[trunk commit] hossman
[
https://issues.apache.org/jira/browse/SOLR-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643063#comment-13643063
]
Stefan Matheis (steffkes) commented on SOLR-4770:
-
Mark, currently we are
Mark Miller created SOLR-4771:
-
Summary: Throw a more specific exception when SLF4J logging jars
cannot be found on the classpath.
Key: SOLR-4771
URL: https://issues.apache.org/jira/browse/SOLR-4771
Patch up.
https://issues.apache.org/jira/browse/SOLR-4771
- Mark
On Apr 26, 2013, at 11:34 AM, Uwe Schindler u...@thetaphi.de wrote:
Unfortunately thats not possible with SFL4J: The „simplicity” of this
framework is based on the fact that the class path can only conatin *one*
logging
[
https://issues.apache.org/jira/browse/SOLR-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-4771:
--
Attachment: SOLR-4771.patch
trivial patch
Throw a more specific exception when SLF4J
[
https://issues.apache.org/jira/browse/SOLR-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643067#comment-13643067
]
Steve Rowe commented on SOLR-4766:
--
I ran the Maven checks from the smoke tester with
[
https://issues.apache.org/jira/browse/SOLR-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643069#comment-13643069
]
Stefan Matheis (steffkes) commented on SOLR-3838:
-
[~jkrupan] would you
[
https://issues.apache.org/jira/browse/SOLR-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Matheis (steffkes) updated SOLR-3838:
Fix Version/s: 4.4
5.0
Assignee: Stefan Matheis
[
https://issues.apache.org/jira/browse/SOLR-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643076#comment-13643076
]
Yonik Seeley commented on SOLR-4754:
FWIW, I also hit this on my OS-X box and my linux
[
https://issues.apache.org/jira/browse/SOLR-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-4754:
---
Priority: Blocker (was: Major)
solrcloud does not detect an implicit host and does not provide
[
https://issues.apache.org/jira/browse/SOLR-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-4754:
---
Fix Version/s: 5.0
4.3
solrcloud does not detect an implicit host and does
On Wed, Apr 24, 2013 at 5:18 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
FWIW: During my testing I did encounter one new bug: SOLR-4754, but since
it has a workarround (and i have no idea yet what the underlying problem
is to even try for a quick fix) I don't think it should block the
[
https://issues.apache.org/jira/browse/SOLR-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643081#comment-13643081
]
Commit Tag Bot commented on SOLR-4705:
--
[branch_4x commit] hossman
[
https://issues.apache.org/jira/browse/LUCENE-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642971#comment-13642971
]
Han Jiang edited comment on LUCENE-3069 at 4/26/13 6:08 PM:
[
https://issues.apache.org/jira/browse/SOLR-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643086#comment-13643086
]
Commit Tag Bot commented on SOLR-4705:
--
[trunk commit] hossman
[
https://issues.apache.org/jira/browse/SOLR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643088#comment-13643088
]
Colin Bartolome commented on SOLR-4455:
---
That workaround seems to work perfectly.
[
https://issues.apache.org/jira/browse/SOLR-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643089#comment-13643089
]
Steve Rowe commented on SOLR-4771:
--
The error message in the patch says Could not find
[
https://issues.apache.org/jira/browse/SOLR-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643103#comment-13643103
]
Commit Tag Bot commented on SOLR-4705:
--
[branch_4x commit] hossman
Upayavira created SOLR-4772:
---
Summary: DateRoundingUpdateProcessorFactory
Key: SOLR-4772
URL: https://issues.apache.org/jira/browse/SOLR-4772
Project: Solr
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SOLR-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bennett closed SOLR-4438.
--
Resolution: Duplicate
Two issues split into new Jira bugs, and linked to bug that fixed legend
[
https://issues.apache.org/jira/browse/SOLR-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643113#comment-13643113
]
Mark Miller commented on SOLR-4754:
---
We need to fix it, and it's def a 4.3 blocker.
[
https://issues.apache.org/jira/browse/SOLR-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned SOLR-4754:
-
Assignee: Mark Miller
solrcloud does not detect an implicit host and does not provide clear
[
https://issues.apache.org/jira/browse/SOLR-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643119#comment-13643119
]
Mark Miller commented on SOLR-4771:
---
Feel free to make some changes - I don't intend on
[
https://issues.apache.org/jira/browse/SOLR-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13643129#comment-13643129
]
Commit Tag Bot commented on SOLR-4705:
--
[lucene_solr_4_3 commit] hossman
1 - 100 of 165 matches
Mail list logo
