It absolutely is a better way to collaborate on development, especially in
conjunction with github:
http://github.com/apache/solr
HOWEVER, the merge of Lucene & Solr has totally disrupted the git mirrors.
Who can fix this?
~ David Smiley
-
Author: https://www.packtpub.com/solr-1-4-enterpri
I work with Maven all the time, and recent Solr releases too. It would be
very useful if Solr SNAPSHOTs could get deployed to
https://repository.apache.org/index.html on an automated basis. Is anyone
opposed to this, and if not, could someone set this up? It would be really
sweet if it were con
Another question...
How do I query for documents that have a point in a lat-lon box (no
scoring/ranking requirements)? If my documents had no more than one point
then I could use current Solr features with a pair of range queries each
going over a float lat field and a lon field. But my docume
This error is with the example docs indexed. Nothing more. I might have
forgotten to commit.
Grant Ingersoll-6 wrote:
>
>
> On Mar 8, 2010, at 5:16 PM, David Smiley @MITRE.org wrote:
>
>>
>> The confusion is that there are multiple issues, each has multiple
>>
lhost:8983/solr/select/?q=_val_:"recip(dist(2, store,
point(34.0232,-81.0664)),1,1,0)"&fl=*,score
I'm on the very latest trunk from minutes ago, and I did a clean before
building Solr.
Grant Ingersoll-6 wrote:
>
>
> On Mar 8, 2010, at 12:45 AM, David Smiley @
Hello folks,
I'm trying to follow all this spatial work going on right now and it's
tough. I'd just like to try it out. I'm on trunk but some of the examples
on the SpatialSearch wiki page error ("Unknown function point in Function
query"). I'm following multiple JIRA issues. Can someone poin
I'll check and if there's a problem then I'll take care of it myself. Thanks
for the nice header on top of my addendum page.
~ David
hossman wrote:
>
>
> : + Available For Purchase...
> : +*
> [[http://www.packtpub.com/solr-1-4-enterprise-search-server?utm_source=http%3A%2F%2Flucene.apache
Yes the book was a ton of work; more than anticipated. Never again, though
maybe an updated edition some day maybe.
Thanks Hoss for clarification and the specific URLs you referenced. It's
awkward to have the site managed in this manner instead of using some sort
of online CMS/publishing webapp
Hello Solr devs. I'd like to see news of my book "Solr 1.4 Enterprise Search
Server" placed on the Solr home page. Yonik suggested that Lucene's home
page would also be suitable. The more people that buy the book, the more
that Apache Software Foundation is supported (5% royalties).
The link t
This is a super-easy request for a Solr commiter to do. Look at line 187 of
FieldType. It catches NumberFormatException (a subtype of RuntimeException)
when calling toInternal() in order to throw a SolrException that has useful
information -- namely the field attempting to be set and its value.
To whomever developed flattenBooleanQuery:
Why is the dismax query being flattened? It would seem that because of
the limited syntax that DisMaxQParserPlugin employs, all you would ever get
is a one-level boolean query but I am probably missing something.
~ David
--
View this message in conte
Actually, Solr depends on Lucene :-)
SLF4J doesn't have a "LogMessage" to propagate to the container since it's a
simple thin facade to the logging kit you want to use. In the case of JUL
which you're a fan of and what we all think should be the default
implementation if you don't take steps to
I'm not following the scenario you are suggesting as it would apply to SLF4J.
I understand that you describe a situation where SLF4J is loaded by both the
container and the webapp (and so they are technically different classes),
but not how this will pose a problem. Logger's are only used intern
Ehh... I don't think anyone would say that "commons logging is such a great
thing" in the first place. You'll find plenty of info to the contrary.
Besides, JCL is targeted at reusable libraries / embedded things and Tomcat
doesn't fit that and so it doesn't use it.
~ David
Shalin Shekhar Manga
>
> [ ] Keep solr logging as is. (JUL)
> [X] Convert solr logging to SLF4J
--
View this message in context:
http://www.nabble.com/Solr-Logging-tp16836646p17028119.html
Sent from the Solr - Dev mailing list archive at Nabble.com.
Today I decided to take matters into my own hands and get jul-log4j-bridge to
work in my JBoss 3.x environment. The experience so far is:
(A) jul-log4j-bridge plus the "apache-log4j-component" library seems
unmaintained and I've seen a question asked of it on a list not get
responded to (that I h
That may meet the functional need but (a) it's unacceptable to the Solr dev's
for the same reason that ANYTHING other than JUL is on principle, and (b)
even someone like me finds the notion of a project specific log manager of
sorts too be worse on principle than any other possible choice (JUL or
I don't know about you, but an issue that continues to flale up now and then
(with a long passionate thread as we are having now) strikes me as "strong
opposition".
If Solr had always used SLF4J (or even JCL), do you imagine there would be
any opposition that compared in any way to the opposition
Hmm. This is probably fixable doing either of these two (both are easy):
1. update the SLF4J in Jetty
2. at deploy time either remove slf4j from the war, or configure Jetty not
to use it (JBoss has that latter feature which is quite nice)
This is also a scenario that could play out with JUL, it'
hossman wrote:
>
> : a fan; but it's really not that important any way). Then, if someone
> (like
> : me :-) would like to configure logging with log4j then I am easily
> empowered
> : to do so by removing that jar and adding slf4j-log4j.jar. What I like
> about
>
> This is the part of all th
hossman wrote:
>
> ...
> There may be servlet containers that don't do a particularly good job of
> dealing with JUL (aka: JDK logging) but that is their deficiency, not
> Solr's.
>
That is a convincing argument, admittedly. But by using SLF4J, Solr won't
alienate users using such contain
I do sympathize; it does seem wrong, but it's the norm in Java because Sun
screwed up Jdk14 logging. It's not a reflection of the design decisions of
Solr (i.e. your judgement) so please don't feel too bad accepting SLF4J.
~ David
Erik Hatcher wrote:
>
> My main point is philosophical - addin
Whenever I see a project with some home-grown LogManager that provides
loggers, I am always mildly disgusted no matter how simple it is (no
disrespect to you, that is my opinion). I believe use of SLF4J will meet
common goals. Solr should log to SLFJ4J (slf4j-api.jar) and then
out-of-the-box shi
23 matches
Mail list logo
