[
https://issues.apache.org/jira/browse/SOLR-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar reassigned SOLR-1316:
---
Assignee: Shalin Shekhar Mangar
Create autosuggest component
I'm not using Embedded Solr directly, I've seen several projects
depending on Lucene as a Maven artifact
and include also a dependency on some solr module as a general
utility, for example to use some solr analysers.
Let's say you had Lucene 2.4.1, when adding solr-analysers version
1.3.0 in the
[
https://issues.apache.org/jira/browse/SOLR-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788664#action_12788664
]
Jean Baptiste Pionnier commented on SOLR-1357:
--
Thank you very much Noble.
My
[
https://issues.apache.org/jira/browse/SOLR-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788664#action_12788664
]
Jean Baptiste Pionnier edited comment on SOLR-1357 at 12/10/09 11:02 AM:
On Dec 10, 2009, at 1:01 AM, Mattmann, Chris A (388J) wrote:
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
[
https://issues.apache.org/jira/browse/SOLR-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788701#action_12788701
]
Shalin Shekhar Mangar commented on SOLR-1316:
-
I've started looking into the
Hi All,
When I do a specific MLT search on a document with debugQuery=True I am getting
a NullPoniterException both on screen and in my catalina logs. The query is as
follows
Hi Grant,
On 12/10/09 3:16 AM, Grant Ingersoll gsing...@apache.org wrote:
I'm not sure this works, as you need to specify the type of the subfield,
which is what Option B does. I don't think inheritance is the what is going
on here, more like delegation, and that isn't necessarily needed
I¹ll try and hold off, but also work on a patch for option (B+)C :)
On 12/10/09 7:37 AM, Grant Ingersoll gsing...@apache.org wrote:
I have Option B implemented at this point, minus a few tests passing. I'll
put up a patch as soon as I get it working.
[
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:
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788800#action_12788800
]
Yonik Seeley commented on SOLR-1131:
bq. Next up: Implement ValueSource support for
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=12788802#action_12788802
]
Yonik Seeley commented on SOLR-1131:
bq. Yonik, could you elaborate on this? It seems
[
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 to
I wouldn't necessarily link FieldType.isPolyField() to the idea of a
poly value source... they are two different things.
For example, if NumericField had not already been written in Lucene, I
would have perhaps just indexed both the lat and lon into the same
lucene field. That part can be more of
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 Thu, Dec 10, 2009 at 1:44 PM, Grant Ingersoll gsing...@apache.org wrote:
[...]
Maybe, there are tradeoffs though.
Let's get concrete and look at the VectorDistanceFunction (dist()). It can
currently take in an even number of ValueSource instances
Geo will be the dominant use of points by
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
[
https://issues.apache.org/jira/browse/SOLR-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788849#action_12788849
]
Mark Miller commented on SOLR-1277:
---
Missed the latest comment - I'm going to commit this
[
https://issues.apache.org/jira/browse/SOLR-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788852#action_12788852
]
Mark Miller commented on SOLR-1277:
---
I've committed some base code to the cloud branch.
[
https://issues.apache.org/jira/browse/SOLR-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788900#action_12788900
]
Yonik Seeley commented on SOLR-1277:
Nice work Mark! I'll try and get what you have up
[
https://issues.apache.org/jira/browse/SOLR-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788913#action_12788913
]
Andrzej Bialecki commented on SOLR-1316:
-
Thanks for the review!
bq. Why do we
[
https://issues.apache.org/jira/browse/SOLR-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788924#action_12788924
]
Patrick Hunt commented on SOLR-1277:
I'm not familiar with solr requirements but, at a
Change name of SOLR749Test
--
Key: SOLR-1642
URL: https://issues.apache.org/jira/browse/SOLR-1642
Project: Solr
Issue Type: Improvement
Components: Build
Affects Versions: 1.4, 1.3
Environment:
[
https://issues.apache.org/jira/browse/SOLR-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann updated SOLR-1642:
Attachment: SOLR-1642.Mattmann.121009.patch.txt
Change name of SOLR749Test
[
https://issues.apache.org/jira/browse/SOLR-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann updated SOLR-1642:
Priority: Trivial (was: Major)
Change name of SOLR749Test
--
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789003#action_12789003
]
Chris A. Mattmann edited comment on SOLR-1131 at 12/10/09 11:08 PM:
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann updated SOLR-1131:
Attachment: SOLR-1131.Mattmann.121009.patch.txt
Hi All:
Here's a cut on the patch. Some
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789003#action_12789003
]
Chris A. Mattmann edited comment on SOLR-1131 at 12/10/09 11:08 PM:
Hi All,
While thinking about SOLR-1131, something important just came to mind. If we
allow poly fields to add fields to the schema (be it via dynamic fields, or
explicit field decls, either way), then we introduce a disconnect between
the existing XML schema, and the runtime schema instance. To
: Subject: Best practices in Solr Schema Design
http://people.apache.org/~hossman/#solr-dev
Please Use solr-u...@lucene Not solr-...@lucene
Your question is better suited for the solr-u...@lucene mailing list ...
not the solr-...@lucene list. solr-dev is for discussing development of
the
: My current thought on #1 is that we probably don't want to change the
: internal lookup mechanism used by IndexSchema unless we gain
: significant power by doing so. I'm not sure I currently see it.
:
: My thoughts on #2 is more on a case-by-case basis. For the simple
: case of a point class
Noble:
1) you *have* to include a CHANGES.txt entry for every non-trivial commit
... if it has a Jira issue, there better be a CHANGES.txt entry, and the
CHANGES.txt entry really needs to be in the same atomic commit as the rest
of the changes, not a follow up commit, so code changes can be
On Thu, Dec 10, 2009 at 6:35 PM, Mattmann, Chris A (388J)
chris.a.mattm...@jpl.nasa.gov wrote:
While thinking about SOLR-1131, something important just came to mind. If we
allow poly fields to add fields to the schema (be it via dynamic fields, or
explicit field decls, either way), then we
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789079#action_12789079
]
Yonik Seeley commented on SOLR-1131:
Quick comment based on a spot check of the changes
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789082#action_12789082
]
Yonik Seeley commented on SOLR-1131:
bq. parsePoint in DistanceUtils, why use ',' as the
Hi Yonik,
While thinking about SOLR-1131, something important just came to mind. If we
allow poly fields to add fields to the schema (be it via dynamic fields, or
explicit field decls, either way), then we introduce a disconnect between
the existing XML schema, and the runtime schema
[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789106#action_12789106
]
Chris A. Mattmann commented on SOLR-1131:
-
{quote}
A comma is more user friendly -
[
https://issues.apache.org/jira/browse/SOLR-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789116#action_12789116
]
Noble Paul commented on SOLR-1621:
--
hi . If everyone is OK I would just cleanup the patch
[
https://issues.apache.org/jira/browse/SOLR-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789120#action_12789120
]
Otis Gospodnetic commented on SOLR-1632:
What about this approach:
[
https://issues.apache.org/jira/browse/SOLR-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789121#action_12789121
]
Noble Paul commented on SOLR-1277:
--
A few comments on the
[
https://issues.apache.org/jira/browse/SOLR-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12789121#action_12789121
]
Noble Paul edited comment on SOLR-1277 at 12/11/09 5:43 AM:
A
remove DIH-extras package
-
Key: SOLR-1643
URL: https://issues.apache.org/jira/browse/SOLR-1643
Project: Solr
Issue Type: Sub-task
Components: contrib - DataImportHandler
Reporter: Noble Paul
[
https://issues.apache.org/jira/browse/SOLR-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar reassigned SOLR-1643:
---
Assignee: Shalin Shekhar Mangar
remove DIH-extras package
[
https://issues.apache.org/jira/browse/SOLR-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-1643:
Attachment: SOLR-1643.patch
Patch for the changes. I'll commit it shortly.
remove
[
https://issues.apache.org/jira/browse/SOLR-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-1643:
Attachment: SOLR-1643.patch
Remove pom and src packaging instructions for extras
[
https://issues.apache.org/jira/browse/SOLR-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-1643.
-
Resolution: Fixed
Committed revision 889519.
remove DIH-extras package
Hey Guys,
Do we need to merge changes to trunk to the cloud branch?
--
Regards,
Shalin Shekhar Mangar.
[
https://issues.apache.org/jira/browse/SOLR-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar reassigned SOLR-1177:
---
Assignee: Shalin Shekhar Mangar (was: Grant Ingersoll)
Distributed
[
https://issues.apache.org/jira/browse/SOLR-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar reassigned SOLR-1610:
---
Assignee: Shalin Shekhar Mangar
Add generics to SolrCache
53 matches
Mail list logo
