[
https://issues.apache.org/jira/browse/SOLR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll reassigned SOLR-445:
Assignee: (was: Grant Ingersoll)
XmlUpdateRequestHandler bad documents mid batch aborts
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1131:
--
Attachment: SOLR-1131.patch
Added Chris's comments.
Allow a single field type to index
[
https://issues.apache.org/jira/browse/SOLR-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789913#action_12789913
]
Grant Ingersoll commented on SOLR-1566:
---
I think we should try to coordinate w/ SOLR
[
https://issues.apache.org/jira/browse/SOLR-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1297:
--
Attachment: SOLR-1297.patch
First crack at a patch. I think it's in pretty good shape, but I
[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789743#action_12789743
]
Grant Ingersoll commented on SOLR-773:
--
Just an update:
# SOLR-1131: aka poly fields
Reporter: Grant Ingersoll
Fix For: 1.5
Once we can sort, filter and boost by functions, it may be the case that the
same function is executed for the same value over and over again. Consider
ways to cache this information.
--
This message is automatically generated by JIRA.
-
You can
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1131:
--
Attachment: SOLR-1131.patch
Missing an in DistanceUtils.parsePoint
Allow a single field type
[
https://issues.apache.org/jira/browse/SOLR-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789804#action_12789804
]
Grant Ingersoll commented on SOLR-1650:
---
I was thinking of a cache whose scope
[
https://issues.apache.org/jira/browse/SOLR-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved SOLR-1297.
---
Resolution: Fixed
Committed revision 889997.
Enable sorting by Function Query
/
++
Adjunct Assistant Professor, Computer Science Department University of
Southern California, Los Angeles, CA 90089 USA
++
--
Grant
I think it is the job of the cloud branch to merge to trunk when ready. I
don't feel strongly about it, but I suspect that applying patches to both all
the time would just complicate things for the people working on the cloud
branch, but I don't feel all that strong about it.
On Dec 11, 2009,
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789240#action_12789240
]
Grant Ingersoll commented on SOLR-1131:
---
{quote}
Quick comment based on a spot check
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789241#action_12789241
]
Grant Ingersoll commented on SOLR-1131:
---
I've got a patch almost ready that brings
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789339#action_12789339
]
Grant Ingersoll commented on SOLR-1131:
---
{quote}
I'm wondering what there is to agree
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789351#action_12789351
]
Grant Ingersoll commented on SOLR-1131:
---
bq. Unfortunately, it's at the cost
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1131:
--
Attachment: SOLR-1131.patch
OK, this is getting a lot closer to ready to commit.
Changes
.
--
Grant Ingersoll
http://www.lucidimagination.com/
Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids) using
Solr/Lucene:
http://www.lucidimagination.com/search
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789526#action_12789526
]
Grant Ingersoll commented on SOLR-1131:
---
I think this is ready to commit. I'd like
[
https://issues.apache.org/jira/browse/SOLR-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll reassigned SOLR-1297:
-
Assignee: Grant Ingersoll
Enable sorting by Function Query
[
https://issues.apache.org/jira/browse/SOLR-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on SOLR-1297 started by Grant Ingersoll.
Enable sorting by Function Query
Key: SOLR-1297
URL
[
https://issues.apache.org/jira/browse/SOLR-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789551#action_12789551
]
Grant Ingersoll commented on SOLR-1297:
---
For this, I think we want to be able to do
/
++
Adjunct Assistant Professor, Computer Science Department University of
Southern California, Los Angeles, CA 90089 USA
++
--
Grant Ingersoll
http://www.lucidimagination.com/
Search
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788751#action_12788751
]
Grant Ingersoll commented on SOLR-1131:
---
{quote}
Seems like SolrQueryParser should use
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1131:
--
Attachment: SOLR-1131.patch
This implements Option B as laid out at:
http
OK, next up:
How to handle the need to create multiple ValueSource instances for a given
poly field? FieldType.getValueSource() only returns a single instance.
I think there are a few options:
1. Change the signature above to return a list of ValueSources. This likely
has back compat.
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788805#action_12788805
]
Grant Ingersoll commented on SOLR-1131:
---
bq. DocValues.getPoint(double[] point)
OK
On Dec 10, 2009, at 12:37 PM, Grant Ingersoll wrote:
OK, next up:
How to handle the need to create multiple ValueSource instances for a given
poly field? FieldType.getValueSource() only returns a single instance.
I think there are a few options:
1. Change the signature above
On Dec 10, 2009, at 1:26 PM, Yonik Seeley wrote:
I wouldn't necessarily link FieldType.isPolyField() to the idea of a
poly value source... they are two different things.
Yep. The word Poly is overloaded here to mean multiple ValueSources, but it
isn't necessarily tied to there being a poly
On Dec 10, 2009, at 1:44 PM, Grant Ingersoll wrote:
On Dec 10, 2009, at 1:26 PM, Yonik Seeley wrote:
I wouldn't necessarily link FieldType.isPolyField() to the idea of a
poly value source... they are two different things.
Yep. The word Poly is overloaded here to mean multiple
On Dec 10, 2009, at 1:54 PM, Grant Ingersoll wrote:
D'oh, I see another way of doing this, namely the Distance functions only
work with points.
Namely, the second case above becomes:
dist(2, point1, point(x1, y1));
So, I went this route and I think it actually plays out quite nice
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
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=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
[
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
[
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
[
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 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
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
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 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
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.
On Dec 8, 2009, at 12:22 AM, Noble Paul നോബിള് नोब्ळ् wrote:
Integrating Extraction w/ DIH is a better option. DIH makes it easier
to do the mapping of fields etc.
Which comment is this directed at? I'm lacking context here.
On Tue, Dec 8, 2009 at 4:59 AM, Grant Ingersoll gsing
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1131:
--
Attachment: SOLR-1131.patch
OK, here's my take on this. I took Yonik's and merged it w
[
https://issues.apache.org/jira/browse/SOLR-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12787113#action_12787113
]
Grant Ingersoll commented on SOLR-1586:
---
FYI, see the SOLR-1131 for an implementation
[
https://issues.apache.org/jira/browse/SOLR-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12787115#action_12787115
]
Grant Ingersoll commented on SOLR-1586:
---
bq. we should have the ability to output
On Dec 7, 2009, at 5:59 PM, Chris Hostetter wrote:
: fieldType name=latlon type=LatLonFieldType pattern=location__* /
: fieldType name=latlon_home type=LatLonFieldType
pattern=location_home_*/
: fieldType name=latlon_work type=LatLonFieldType
pattern=location_home_*/
:
: field
On Dec 7, 2009, at 6:13 PM, Chris Hostetter wrote:
: I'm not sure if you worry about it. But I'd argue it isn't natural
: anyway. You would do the following instead, which is how any address
: book I've ever seen works:
: field name=home type=LatLonFT/
: field name=work type=LatLonFT/
On Dec 7, 2009, at 3:51 PM, Chris Hostetter wrote:
ASs someone with very little knowledge of Solr Cell and/or Tika, I find
myself wondering if ExtractingRequestHandler would make more sense as an
extractingUpdateProcessor -- where it could be configured to take take either
binary fields
[
https://issues.apache.org/jira/browse/SOLR-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12787198#action_12787198
]
Grant Ingersoll commented on SOLR-1586:
---
Can you put a patch containing just
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12786586#action_12786586
]
Grant Ingersoll commented on SOLR-1131:
---
Hey Yonik,
One of the things I was debating
On Dec 3, 2009, at 4:48 PM, Mark Miller wrote:
Oh well though. So it goes. Its Apache - they could package it all up,
hide the code under the covers, put a notice saying some work was
derived from Solr, call it Solr: geo search edition,
Actually, no, they cannot call it Solr: geo search
Type: New Feature
Components: search
Reporter: Grant Ingersoll
Priority: Minor
It would be really cool if we could have a QueryComponent that enabled doing
aggregating calculations on search results similar to what the StatsComponent
does, but in a more generic
[
https://issues.apache.org/jira/browse/SOLR-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12784705#action_12784705
]
Grant Ingersoll commented on SOLR-1277:
---
Mark,
I think this makes sense. I think you
[
https://issues.apache.org/jira/browse/SOLR-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12784948#action_12784948
]
Grant Ingersoll commented on SOLR-1277:
---
bq. Is there a benefit to refactoring
On Dec 1, 2009, at 1:42 AM, Chris Hostetter wrote:
It feels like something we've overlooked in this discussion is whether we
need to worry about any FieldType API changes needed to make these new
PolyField classes aware of when they are multivalued.
The API suggestions grant made gives
On Nov 28, 2009, at 7:37 PM, Chris Hostetter wrote:
: I don't think it's useful to somehow programmatically access the list
: of fields that a fieldType could output.
based on my understanding of the potential types of use cases we're
talking about, i think i agree with you. It seems
On Nov 28, 2009, at 3:45 AM, Erik Hatcher wrote:
What about rather than conflating field types for creating multiple fields,
use update processors to do the this expansion instead?
How do you maintain the semantic information needed at search time? Are you
still having the field type (or
On Nov 25, 2009, at 8:24 PM, Chris Hostetter wrote:
I'm having a hard time wrapping my head arround this entire concept ... i
know part of my problem is that your example use case seems somewhat
nonsensical...
: As a simple proof of concept, imagine that I define a new FieldType
:
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1131:
--
Fix Version/s: 1.5
Allow a single field type to index multiple fields
Hey Devs,
(Sorry for the length, but this patch has a lot of touch points and I think it
needs discussion. I think it really can open up some new possibilities in
Solr, too)
I'm working on https://issues.apache.org/jira/browse/SOLR-1131. I was able to
take Ryan's patch and make some
[
https://issues.apache.org/jira/browse/SOLR-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781945#action_12781945
]
Grant Ingersoll commented on SOLR-1586:
---
Hey Chris,
I'm not sure we want to bring
On Nov 24, 2009, at 9:07 AM, Colin Hynes wrote:
Just to toss in my two cents...
I'd have to agree with Hoss here. In terms of versioning, I see no reason
that a major version bump in a dependency should cause a major version bump
in Solr - unless said bump causes major changes.
It's got
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781948#action_12781948
]
Grant Ingersoll commented on SOLR-1131:
---
See discussion at
http
[
https://issues.apache.org/jira/browse/SOLR-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781973#action_12781973
]
Grant Ingersoll commented on SOLR-1586:
---
Also, where does this patch actually encode
On Nov 19, 2009, at 9:31 AM, Yonik Seeley wrote:
What should the next version of Solr be?
Options:
- have a Solr 2.0 with a lucene 3.x
+1. This gives us a chance to remove some deprecated stuff, too.
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1131:
--
Attachment: SOLR-1131.patch
Starting to add unit tests. Still no support on the search
[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781145#action_12781145
]
Grant Ingersoll commented on SOLR-773:
--
bq. Grant is doing some fantastic work here
[
https://issues.apache.org/jira/browse/SOLR-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved SOLR-1567.
---
Resolution: Fixed
Committed revision 883095.
Upgrade to Tika 0.5
[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781159#action_12781159
]
Grant Ingersoll commented on SOLR-773:
--
Not so much a re-arch, but an extension of some
[
https://issues.apache.org/jira/browse/SOLR-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781193#action_12781193
]
Grant Ingersoll commented on SOLR-1586:
---
Sounds good, but how are you going to deal
Looking at the code that is one consumer of this, FieldType.createField, it
seems like it is a usually handled through a RuntimeException.
On Nov 22, 2009, at 1:47 PM, Mattmann, Chris A (388J) wrote:
Hey Guys,
I'm working on SOLR-1586, and looking at FieldType#toInternal, it just
dawned on
[
https://issues.apache.org/jira/browse/SOLR-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781215#action_12781215
]
Grant Ingersoll commented on SOLR-1586:
---
I'm not sure what good that does to put a lat
[
https://issues.apache.org/jira/browse/SOLR-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781262#action_12781262
]
Grant Ingersoll commented on SOLR-1586:
---
I'd say wait until SOLR-1131 is done
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1131:
--
Summary: Allow a single field type to index multiple fields (was: Allow a
single field
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12780950#action_12780950
]
Grant Ingersoll commented on SOLR-1131:
---
bq. Is this a good idea?
Not sure yet.
bq
: Improvement
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
Fix For: 1.5
Per the TODOs in QueryComponent, create a ShardsComponent that handles setting
up the shards. Additionally, make it so that it can handle smaller parameters,
too. For instance
Create Spatial Point FieldTypes
---
Key: SOLR-1586
URL: https://issues.apache.org/jira/browse/SOLR-1586
Project: Solr
Issue Type: Improvement
Reporter: Grant Ingersoll
Assignee: Grant
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12780954#action_12780954
]
Grant Ingersoll commented on SOLR-1131:
---
I'm also looking for ideas on how to handle
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12780954#action_12780954
]
Grant Ingersoll edited comment on SOLR-1131 at 11/21/09 12:11 PM
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12780956#action_12780956
]
Grant Ingersoll commented on SOLR-1131:
---
I definitely agree, Chris, the interesting
Facet by Function
-
Key: SOLR-1581
URL: https://issues.apache.org/jira/browse/SOLR-1581
Project: Solr
Issue Type: New Feature
Reporter: Grant Ingersoll
Fix For: 1.5
It would be really great if we
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll reassigned SOLR-1131:
-
Assignee: Grant Ingersoll
Allow a single field to index multiple fields
Reporter: Grant Ingersoll
Assignee: Grant Ingersoll
Priority: Trivial
In DocumentBuilder, around lines 267, the BinaryField is created, but it is
never assigned to the field that is added to the output.
--
This message is automatically generated by JIRA.
-
You can
[
https://issues.apache.org/jira/browse/SOLR-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved SOLR-1582.
---
Resolution: Fixed
Fix Version/s: 1.5
committed.
DocumentBuilder does not properly
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1131:
--
Attachment: SOLR-1131.patch
Brings it up to trunk. Still needs test cases. All other tests
[
https://issues.apache.org/jira/browse/SOLR-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12779955#action_12779955
]
Grant Ingersoll commented on SOLR-1574:
---
+1. This was my first time writing functions
Develop a Spatial Query Parser
--
Key: SOLR-1578
URL: https://issues.apache.org/jira/browse/SOLR-1578
Project: Solr
Issue Type: New Feature
Reporter: Grant Ingersoll
Fix For: 1.5
Given
On FieldType, the getValueSource(SchemaField, QParser) implementation just
calls the deprecated getValueSource(SchemaField) method.
/** called to get the default value source (normally, from the
* Lucene FieldCache.)
*/
public ValueSource getValueSource(SchemaField field, QParser
URL?
Thanks,
Pradeep.
--
Grant Ingersoll
http://www.lucidimagination.com/
Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids) using
Solr/Lucene:
http://www.lucidimagination.com/search
[
https://issues.apache.org/jira/browse/SOLR-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1568:
--
Attachment: CartesianTierQParserPlugin.java
Here's the start of a QParserPlugin
[
https://issues.apache.org/jira/browse/SOLR-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12779662#action_12779662
]
Grant Ingersoll commented on SOLR-1568:
---
Honestly, it's a bit tricky and I'm not sure
Any idea on how to pass string constants to a function?
When I do I get:
java.lang.RuntimeException: Exception during query
at
org.apache.solr.util.AbstractSolrTestCase.assertQ(AbstractSolrTestCase.java:218)
at
Allow literal Strings in functions
--
Key: SOLR-1569
URL: https://issues.apache.org/jira/browse/SOLR-1569
Project: Solr
Issue Type: Bug
Reporter: Grant Ingersoll
Assignee: Grant
[
https://issues.apache.org/jira/browse/SOLR-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12778874#action_12778874
]
Grant Ingersoll commented on SOLR-1569:
---
See
http://www.lucidimagination.com/search
https://issues.apache.org/jira/browse/SOLR-1569
On Nov 17, 2009, at 7:08 AM, Grant Ingersoll wrote:
Any idea on how to pass string constants to a function?
When I do I get:
java.lang.RuntimeException: Exception during query
at
org.apache.solr.util.AbstractSolrTestCase.assertQ
[
https://issues.apache.org/jira/browse/SOLR-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1569:
--
Attachment: SOLR-1569.patch
Allow literal Strings in functions
[
https://issues.apache.org/jira/browse/SOLR-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved SOLR-1569.
---
Resolution: Fixed
Committed revision 881319.
Allow literal Strings in functions
201 - 300 of 1390 matches
Mail list logo
