[
https://issues.apache.org/jira/browse/SOLR-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1621:
-
Attachment: SOLR-1621.patch
with ALIAS deprecated
Allow current single core deployments to be specified
[
https://issues.apache.org/jira/browse/SOLR-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12787968#action_12787968
]
Noble Paul commented on SOLR-1621:
--
also deprecated specifying solrconfig from web.xml. We
Why is Solr not depending directly on Lucene but repackaging the same classes?
Sorry I've probably missed some important discussion. Whatever the
reason for this decision, is it still a good reason?
This gets new users in a hell of trouble sometimes, as some
applications introduce Solr after
NPE when uniqueKey is not specified in schema
-
Key: SOLR-1638
URL: https://issues.apache.org/jira/browse/SOLR-1638
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
On Wed, Dec 9, 2009 at 3:33 PM, Sanne Grinovero
sanne.grinov...@gmail.comwrote:
Why is Solr not depending directly on Lucene but repackaging the same
classes?
Solr does depend on Lucene jars. We strive to package officially released
Lucene artifacts but sometimes the release schedule of
[
https://issues.apache.org/jira/browse/SOLR-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788047#action_12788047
]
Uri Boness commented on SOLR-1625:
--
regexp vs. regex - I really don't know. I always use/d
[
https://issues.apache.org/jira/browse/SOLR-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akshay K. Ukey updated SOLR-1638:
-
Attachment: SOLR-1638.patch
NPE when uniqueKey is not specified in schema
[
https://issues.apache.org/jira/browse/SOLR-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-785.
Resolution: Fixed
Committed revision 888796.
Thanks Matthew!
Distributed
[
https://issues.apache.org/jira/browse/SOLR-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akshay K. Ukey updated SOLR-1358:
-
Attachment: SOLR-1358.patch
Integration of Tika and DataImportHandler
In SOLR-1586, the proposed patch introduces the concept that a Solr response
can declare a namespace for part of the response (in this case, it is using the
tags defined by georss.org to specify a point, etc.). I'm not sure what to
make of this. My gut reaction says no, but I'm not a
[
https://issues.apache.org/jira/browse/SOLR-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788089#action_12788089
]
Akshay K. Ukey commented on SOLR-1358:
--
Patch with fix for avoiding reading from data
Hi,
While searching (querying) the solr, how can we achieved following
scenario.
Search priority should be in the following order:
1. Genre
2. nowplaying
3. Stationname
4. Keywords
Say I am searching for rock it should search in genre field first
and then nowplaying
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788103#action_12788103
]
Yonik Seeley commented on SOLR-1131:
bq. 1. Why is TextField overriding getFieldQuery
Hi Grant, and others,
My 2 cents (and of course I'm bias having prepared the patch):
In SOLR-1586, the proposed patch introduces the concept that a Solr response
can declare a namespace for part of the response (in this case, it is using
the tags defined by georss.org to specify a point,
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788113#action_12788113
]
Yonik Seeley commented on SOLR-1131:
Some minor nits about tests in general that I've
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788116#action_12788116
]
Chris A. Mattmann commented on SOLR-1131:
-
Hi Yonik:
I agree in general with your
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788117#action_12788117
]
Yonik Seeley commented on SOLR-1131:
Please see the DocumentBuilder changes I had
Inline...
On Dec 9, 2009, at 9:33 AM, Mattmann, Chris A (388J) wrote:
Hi Grant, and others,
My 2 cents (and of course I'm bias having prepared the patch):
In SOLR-1586, the proposed patch introduces the concept that a Solr response
can declare a namespace for part of the response (in
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788119#action_12788119
]
Yonik Seeley commented on SOLR-1131:
Regarding polyfields... it's not clear why they are
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788121#action_12788121
]
Grant Ingersoll commented on SOLR-1131:
---
bq. IMO, unit tests can be too low level.
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788123#action_12788123
]
Grant Ingersoll commented on SOLR-1131:
---
{quote}
Regarding polyfields... it's not
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788125#action_12788125
]
Yonik Seeley commented on SOLR-1131:
bq. I need to update my IntelliJ Live Templates, as
Hi Grant,
My replies inline as well:
Discussion points:
1. If there are standard namespaces, then people can use them to do fun XML
things
+1. This includes things like validation,
Yeah, but the rest of Solr's response doesn't have it, so...
You mean the rest of SOLR's default
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788138#action_12788138
]
Yonik Seeley commented on SOLR-1131:
bq. poly fields feel like a hybrid between regular
Hey All,
1. Namespaces are fun especially when you have some target format you are
trying to work towards. Many target formats use namespaces extensively so
having the ability to map to them on the back end (response) would be great.
This does not mean that Solr would have to utilize
My gut feeling is that we should not be introducing namespaces by default.
It introduces a new requirement of XML parsers in clients, and some
parsers would start validating by default, and going out to the web to
retrieve the referenced namespace/schema, etc.
I think the initial geosearch
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788151#action_12788151
]
Grant Ingersoll commented on SOLR-1131:
---
bq. What if, instead, dynamic fields are
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788156#action_12788156
]
Yonik Seeley commented on SOLR-1131:
bq. That then requires those dynamic fields to be
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788163#action_12788163
]
Grant Ingersoll commented on SOLR-1131:
---
{quote}
Also, you have subFieldType=double in
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788164#action_12788164
]
Yonik Seeley commented on SOLR-1131:
Perhaps we should return to the design level a bit
Please do not cross-post to the dev and user's list. This kind of question
is appropriate to the users list only.
Best
Erick
On Wed, Dec 9, 2009 at 8:55 AM, Doddamani, Prakash
prakash.doddam...@corp.aol.com wrote:
Hi,
While searching (querying) the solr, how can we achieved following
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788168#action_12788168
]
Chris A. Mattmann commented on SOLR-1131:
-
{quote}
Perhaps we should return to the
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788170#action_12788170
]
Grant Ingersoll edited comment on SOLR-1131 at 12/9/09 5:18 PM:
On Wed, Dec 9, 2009 at 11:44 AM, Mattmann, Chris A (388J)
chris.a.mattm...@jpl.nasa.gov wrote:
How does it introduce any new requirements? Namespaces are easily ignored by
any XML client as they are if they weren't present. In other words, unless
the XML client has setValidating=true, then this
Should have tried this before... I just created a small XML file:
foo
barhi/bar
/foo
I pointed both firefox and IE at this file and it displays as XML fine.
I then changed the file to this:
foo
zoo:barhi/zoo:bar
/foo
That made both of them barf.
That alone makes me lean pretty strongly
Hi Yonik,
Should have tried this before... I just created a small XML file:
foo
barhi/bar
/foo
I pointed both firefox and IE at this file and it displays as XML fine.
I then changed the file to this:
foo
zoo:barhi/zoo:bar
/foo
Sure, of course it does. It's because that's not
On Wed, Dec 9, 2009 at 12:40 PM, Mattmann, Chris A (388J)
chris.a.mattm...@jpl.nasa.gov wrote:
foo
zoo:bar xmlns:zoo=http://example.com/zoo;hi/zoo:bar
/foo
If you're forced to declare the namespace / put the URI, I'm just
afraid of what clients / XML parsers out there may start trying to
this need to be reverted . there was data loss
On Wed, Dec 9, 2009 at 8:46 PM, Apache Wiki wikidi...@apache.org wrote:
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Solr Wiki for change
notification.
The DataImportHandler page has been changed by DNaber.
: I think the initial geosearch feature can start off with
: str10,20/str for a point.
+1.
The current XML format SOlr uses was designed to be extremely simple, very
JSON-esque, and easily parsable by *anyone* in any langauge, without
needing special knowledge of types . It has been heavily
: ...unless things have changed since hte last time i looked, all of the
: out of the box response writers call toString() on any object they
: don't understand. So the best way to move forward in a flexible manner
: seems like it would be to add a new GeoPoint object to Solr, which
:
: I'm not really understanding the value of an approach like that. for
: starters, what Lucene field names would ultimately be created in those
: examples?
:
: The first field would be named location__location.
: The second field would be named location_home_location_home.
: The third
Hi Yonik,
I've run across cases where I added a schema declaration to an XML
file and then things started failing. I think some parsers may
default to validating if it sees that it can?
I've seen this too. But it won't affect the interaction we're talking about
like I said, SOLR-1586
: fieldType name=point type=solr.PointType dimension=2
subFieldType=double/
: field name=home type=point indexed=true stored=true/
...
: And a new document of:
: doc
: field name=point39.0 -79.434/field
: /doc
:
: There are three fields created:
: home -- Contains the stored value
:
: That's not how the Cartesian Field stuff works, but I think I see what
: you are getting at and I would say I'm going to explicitly punt on that
: right now. Ultimately, I think when such a case comes up, the FieldType
: needs to be configured to be able to determine this information.
I'm
On Dec 9, 2009, at 2:04 PM, Chris Hostetter wrote:
: fieldType name=point type=solr.PointType dimension=2
subFieldType=double/
: field name=home type=point indexed=true stored=true/
...
: And a new document of:
: doc
: field name=point39.0 -79.434/field
: /doc
:
: There are
Any parser that does that is so broken that you should stop using it
immediately. --wunder
Walter, totally agree here.
Cheers,
Chris
++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA
I haven't followed this whole thread... but I wanted to point out that
it probably intersects with the review of grant's latest patch that I
did here: https://issues.apache.org/jira/browse/SOLR-1131
I did want to cut'n'paste something from that post:
: I do want to separate these two issues
Hey All,
I think Eric is right on here and what I thought the intent of the patch was.
Facilitating integration of Solr into environments where there is not one true
XML output. In addition, there shouldn't be one true JSON output for cases
where your existing code already has a way it expects
Hi All,
: fieldType name=point type=solr.PointType dimension=2
subFieldType=double/
: field name=home type=point indexed=true stored=true/
...
: And a new document of:
: doc
: field name=point39.0 -79.434/field
: /doc
:
: There are three fields created:
: home -- Contains the
On Wed, Dec 9, 2009 at 2:41 PM, Yonik Seeley yo...@lucidimagination.com wrote:
So... the question is, do we have a concrete alternative to this that
is well fleshed out?
I do, I do... just a little variant that is geo specific and hence
results in nicer names :-)
fieldType name=point
On Dec 9, 2009, at 11:11 AM, Mattmann, Chris A (388J) wrote:
Any parser that does that is so broken that you should stop using it
immediately. --wunder
Walter, totally agree here.
To elaborate my position:
1. Validation is a user option. The XML spec makes that very clear. We've had
10
Missleading error message when dataimport.properties is not writable
Key: SOLR-1639
URL: https://issues.apache.org/jira/browse/SOLR-1639
Project: Solr
Issue Type: Bug
On Dec 9, 2009, at 2:46 PM, Yonik Seeley wrote:
On Wed, Dec 9, 2009 at 2:41 PM, Yonik Seeley yo...@lucidimagination.com
wrote:
So... the question is, do we have a concrete alternative to this that
is well fleshed out?
I do, I do... just a little variant that is geo specific and hence
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788298#action_12788298
]
Grant Ingersoll commented on SOLR-1131:
---
bq. OK... so the real issue is that this
On Wed, Dec 9, 2009 at 3:21 PM, Grant Ingersoll gsing...@apache.org wrote:
Additionally, how do you deal w/ a point in a 3D (or n-D) space?
I guess you would go back to the way you did it (0,1,etc). This was
really just a naming variation, not really a different approach.
I just don't see why
On Dec 9, 2009, at 3:47 PM, Yonik Seeley wrote:
I thought I defined it well... hmmm.
I'll take another stab, outlining using dynamic fields in both
scenarios (explicitly defined dynamic fields, and automatically
defined as part of the creation of the point class). I think we
really do
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788307#action_12788307
]
Grant Ingersoll commented on SOLR-1131:
---
Note, I don't think the distance function
On Wed, Dec 9, 2009 at 3:49 PM, Grant Ingersoll gsing...@apache.org wrote:
On Dec 9, 2009, at 3:47 PM, Yonik Seeley wrote:
I thought I defined it well... hmmm.
I'll take another stab, outlining using dynamic fields in both
scenarios (explicitly defined dynamic fields, and automatically
On Dec 9, 2009, at 3:52 PM, Yonik Seeley wrote:
On Wed, Dec 9, 2009 at 3:49 PM, Grant Ingersoll gsing...@apache.org wrote:
On Dec 9, 2009, at 3:47 PM, Yonik Seeley wrote:
I thought I defined it well... hmmm.
I'll take another stab, outlining using dynamic fields in both
scenarios
[
https://issues.apache.org/jira/browse/SOLR-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher updated SOLR-1639:
---
Summary: Misleading error message when dataimport.properties is not
writable (was: Missleading error
Proposal for handling points using only the field lookup mechanisms
currently in place in IndexSchema:
Option A: dynamic fields used for subfields, those dynamic fields need
to be explicitly defined in the XML
// needed
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788319#action_12788319
]
Yonik Seeley commented on SOLR-1131:
Aside: it looks like the code for getFieldOrNull
OK, I'm fine w/ taking this type of approach, as opposed to the lookup
mechanism I have. Of the two laid out below, there are pros and cons to both,
as I see it.
I'm inclined towards Option B. This keeps it hidden from the user, but
doesn't require extra work for Solr. Let me code it up.
[
https://issues.apache.org/jira/browse/SOLR-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uri Boness updated SOLR-1625:
-
Attachment: SOLR-1625.patch
Updated the patch to support the following changes (as discussed above):
-
it is now impossible to edit the DIH wiki page becaus
eofhttps://issues.apache.org/jira/browse/INFRA-2270
We have to be constantly vigilant of somebody editing that page
because any editing results in loss of data. How do we go about with
this?
--
Hi Yonik et al.,
I¹d like to add:
Option C: Sub fields are specified as a attribute on the fieldType tag
// needed to essentially define the point type
fieldType name=latlon class=GeoPoint subFieldSuffix=_latlon ../
Hi Yonik,
Using standards enables standard tool development.
We do use standards... lots of them :-) Let's be a bit more specific
though - I was asking about using a namespace for the point type by
*default*, and in isolation (i.e. the rest of solr xml isn't
namespaced), and if/how that
Register VelocityResponseWriter automatically in example solrconfig.xml
---
Key: SOLR-1640
URL: https://issues.apache.org/jira/browse/SOLR-1640
Project: Solr
Issue Type:
[
https://issues.apache.org/jira/browse/SOLR-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar reassigned SOLR-1638:
---
Assignee: Shalin Shekhar Mangar
NPE when uniqueKey is not specified in
[
https://issues.apache.org/jira/browse/SOLR-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar reassigned SOLR-1639:
---
Assignee: Shalin Shekhar Mangar
Misleading error message when
[
https://issues.apache.org/jira/browse/SOLR-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-1638.
-
Resolution: Fixed
Committed revision 889115.
Thanks Akshay!
NPE when uniqueKey
Add UI for Solr Core Admin
--
Key: SOLR-1641
URL: https://issues.apache.org/jira/browse/SOLR-1641
Project: Solr
Issue Type: New Feature
Components: web gui
Reporter: Erik Hatcher
[
https://issues.apache.org/jira/browse/SOLR-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788555#action_12788555
]
Erik Hatcher commented on SOLR-1641:
VelocityResponseWriter might be the way to go with
[
https://issues.apache.org/jira/browse/SOLR-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-1639:
Attachment: SOLR-1639.patch
If file could not be written, add a severe message to
[
https://issues.apache.org/jira/browse/SOLR-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-1639:
Affects Version/s: 1.4
Misleading error message when dataimport.properties is not
75 matches
Mail list logo
