[
https://issues.apache.org/jira/browse/SOLR-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1352:
-
Attachment: SOLR-1352.patch
first cut an ugly patch. a lot of work left before putting it in
DIH:
[
https://issues.apache.org/jira/browse/SOLR-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1352:
-
Description:
It has been a long pending request to make DIH multithreaded. Now that we have
implemented
[
https://issues.apache.org/jira/browse/SOLR-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll reassigned SOLR-1561:
-
Assignee: Grant Ingersoll
Import Lucene 2.9.1 Geospatial JAR
Import Lucene 2.9.1 Geospatial JAR
--
Key: SOLR-1561
URL: https://issues.apache.org/jira/browse/SOLR-1561
Project: Solr
Issue Type: New Feature
Reporter: Grant Ingersoll
Priority:
[
https://issues.apache.org/jira/browse/SOLR-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1561:
--
Fix Version/s: 1.5
Import Lucene 2.9.1 Geospatial JAR
--
[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on SOLR-773 started by Grant Ingersoll.
Incorporate Local Lucene/Solr
-
Key: SOLR-773
URL:
[
https://issues.apache.org/jira/browse/SOLR-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved SOLR-1561.
---
Resolution: Fixed
Import Lucene 2.9.1 Geospatial JAR
--
[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777549#action_12777549
]
Gijs Kunze commented on SOLR-773:
-
I've written a Solr plugin which uses a field with the
[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777582#action_12777582
]
Thomas Woodard commented on SOLR-236:
-
I'm trying to get field collapsing to work against
Implementing my first function (distance stuff) and notices that functions seem
to have a float bent to them. Not even sure what would be involved, but there
are cases for distance that I could see wanting double precision. Thoughts?
-Grant
On Fri, Nov 13, 2009 at 12:52 PM, Grant Ingersoll gsing...@apache.org wrote:
Implementing my first function (distance stuff) and notices that functions
seem to have a float bent to them. Not even sure what would be involved, but
there are cases for distance that I could see wanting double
Float is almost never good enough. The loss of precision is horrific.
wunder
On Nov 13, 2009, at 9:58 AM, Yonik Seeley wrote:
On Fri, Nov 13, 2009 at 12:52 PM, Grant Ingersoll gsing...@apache.org wrote:
Implementing my first function (distance stuff) and notices that functions
seem to have
[
https://issues.apache.org/jira/browse/SOLR-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher updated SOLR-1561:
---
Description: Bring in the spatial contrib jar so that we can use its
utilities, etc. where
On Nov 13, 2009, at 12:58 PM, Yonik Seeley wrote:
On Fri, Nov 13, 2009 at 12:52 PM, Grant Ingersoll gsing...@apache.org wrote:
Implementing my first function (distance stuff) and notices that functions
seem to have a float bent to them. Not even sure what would be involved,
but there are
On Fri, Nov 13, 2009 at 1:01 PM, Walter Underwood wun...@wunderwood.org wrote:
Float is almost never good enough. The loss of precision is horrific.
Are you saying it's not good enough for this case (the final answer of
a relative distance calculation)?
7 digits of precision is enough to
On Fri, Nov 13, 2009 at 1:31 PM, Grant Ingersoll gsing...@apache.org wrote:
Yeah, in the end, Lucene Scorer returns a float... However, if we allow for
pseudo fields and other capabilities, it would be nice to have doubles.
We have doubles already... It's just that our general purpose
Float is often OK until you try and use it for further calculation. Maybe it is
good enough for printing out distance, but maybe not for further use.
wunder
On Nov 13, 2009, at 10:32 AM, Yonik Seeley wrote:
On Fri, Nov 13, 2009 at 1:01 PM, Walter Underwood wun...@wunderwood.org
wrote:
If I implement Vincenty's formula for distance between two points on an
ellipsoid that can be accurate down to the 0.5mm. Not doing that yet and not
planning on implementing, so this is not a huge issue right now.
Still, I think we should put it on our roadmap.
On Nov 13, 2009, at 1:32 PM,
On Nov 13, 2009, at 1:35 PM, Yonik Seeley wrote:
On Fri, Nov 13, 2009 at 1:31 PM, Grant Ingersoll gsing...@apache.org wrote:
Yeah, in the end, Lucene Scorer returns a float... However, if we allow for
pseudo fields and other capabilities, it would be nice to have doubles.
We have doubles
Folks,
I am trying to get Lucene MMAP to work in solr.
I am assuming that when I configure MMAP the entire index will be loaded
into RAM.
Is that the right assumption ?
I have tried the following ways for using MMAP:
Option 1. Using the solr config below for MMAP configuration
On 11/13/09 11:38 AM, Grant Ingersoll gsing...@apache.org wrote:
If I implement Vincenty's formula for distance between two points on an
ellipsoid that can be accurate down to the 0.5mm. Not doing that yet and not
planning on implementing, so this is not a huge issue right now.
Still, I
Functions should better support double values
-
Key: SOLR-1562
URL: https://issues.apache.org/jira/browse/SOLR-1562
Project: Solr
Issue Type: Improvement
Reporter: Grant Ingersoll
On Nov 13, 2009, at 1:48 PM, Mattmann, Chris A (388J) wrote:
Still, I think we should put it on our roadmap.
SOLR-1562.
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 internals of the Solr application ... it is *not* the
[
https://issues.apache.org/jira/browse/SOLR-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777648#action_12777648
]
Chris A. Mattmann commented on SOLR-1302:
-
Hey Grant,
I'd love to help on this
[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777649#action_12777649
]
Martijn van Groningen commented on SOLR-236:
Thomas, the method that cannot be
: So which would be appropriate? My concern is that the 1.4.1 has a larger
: file size so don't want to miss some 1.4 feature or bug fix that happened
I don't understand this question ... what do you mean by 1.4.1 has a
larger file size ?
building 1.4.0 from the source in the official release
: The UpdateCSV page has been changed by kristopolous.
: The comment on this change is: grammar.
: http://wiki.apache.org/solr/UpdateCSV?action=diffrev1=13rev2=14
Did someone revert this change? ... i was going to (since the old version
was actually correct) but the wiki says the current
On Fri, Nov 13, 2009 at 3:55 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
: The UpdateCSV page has been changed by kristopolous.
: The comment on this change is: grammar.
: http://wiki.apache.org/solr/UpdateCSV?action=diffrev1=13rev2=14
Did someone revert this change? ... i was going
[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777659#action_12777659
]
Thomas Woodard commented on SOLR-236:
-
I tried the build again, and you are right, it
[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777659#action_12777659
]
Thomas Woodard edited comment on SOLR-236 at 11/13/09 9:10 PM:
---
: Good question... I tried to revert it too when I first saw it.
: The live page actually showed the new edited version, but every time I
: tried to edit it, I got the old text. Eventually, the live page
: showed the old version. The history never showed the new edit AFAIK.
: Was going to bring
[
https://issues.apache.org/jira/browse/SOLR-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777674#action_12777674
]
Hoss Man commented on SOLR-1432:
bq. I wish this issue would have been called out in the
[
https://issues.apache.org/jira/browse/SOLR-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777676#action_12777676
]
Grant Ingersoll commented on SOLR-1302:
---
I've got Haversine implemented (great
That is fine we are using 1.4.0. When I compiled the 1.4.1 was 2k extra in
size.
--
Jeff Newburn
Software Engineer, Zappos.com
jnewb...@zappos.com - 702-943-7562
From: Chris Hostetter hossman_luc...@fucit.org
Reply-To: solr-dev@lucene.apache.org
Date: Fri, 13 Nov 2009 12:47:34 -0800 (PST)
[
https://issues.apache.org/jira/browse/SOLR-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1302:
--
Attachment: SOLR-1302.patch
Haversine implementation, RadianFunction and DegreeFunction. Also
[
https://issues.apache.org/jira/browse/SOLR-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1227#action_1227
]
Grant Ingersoll commented on SOLR-1302:
---
Note, we may want to mod this to work more
NPE's occur in various situations related to FIeldable.stringValue when
upgrading from 1.3 to 1.4
-
Key: SOLR-1563
URL:
[
https://issues.apache.org/jira/browse/SOLR-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1285#action_1285
]
Hoss Man commented on SOLR-1563:
First anecdotal NPE stack trace reported by Jake Brownell
[
https://issues.apache.org/jira/browse/SOLR-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1286#action_1286
]
Hoss Man commented on SOLR-1563:
Second anecdotal exception reported by Solr Trey, also
[
https://issues.apache.org/jira/browse/SOLR-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1288#action_1288
]
Hoss Man commented on SOLR-1563:
The following stack trace was generated using Solr 1.4, and
[
https://issues.apache.org/jira/browse/SOLR-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1290#action_1290
]
Hoss Man commented on SOLR-1563:
These stack traces demonstrate similar NPE exceptions when
[
https://issues.apache.org/jira/browse/SOLR-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1292#action_1292
]
Hoss Man commented on SOLR-1563:
In all of the stack traces listed above, the NPE seems to
43 matches
Mail list logo
