[jira] Created: (SOLR-2033) Response parsing fragility in solrj

Response parsing fragility in solrj --- Key: SOLR-2033 URL: https://issues.apache.org/jira/browse/SOLR-2033 Project: Solr Issue Type: Bug Components: clients - java Affects Versions: 1.4.1

[jira] Resolved: (LUCENE-2118) Intermittent failure in TestIndexWriterMergePolicy.testMaxBufferedDocsChange

[ https://issues.apache.org/jira/browse/LUCENE-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2118. Fix Version/s: 3.1 Resolution: Fixed > Intermittent failure in TestIndexWri

[jira] Commented: (LUCENE-2118) Intermittent failure in TestIndexWriterMergePolicy.testMaxBufferedDocsChange

[ https://issues.apache.org/jira/browse/LUCENE-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896287#action_12896287 ] Michael McCandless commented on LUCENE-2118: I found the root cause here; it's

[jira] Commented: (SOLR-2032) Map-viewer demo of SolrSpatial test data

[ https://issues.apache.org/jira/browse/SOLR-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896283#action_12896283 ] Lance Norskog commented on SOLR-2032: - >From the [Google Maps >FAQ|http://code.google.c

[jira] Resolved: (LUCENE-1183) TRStringDistance uses way too much memory (with patch)

[ https://issues.apache.org/jira/browse/LUCENE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir resolved LUCENE-1183. - Resolution: Fixed Committed revision 983298 (trunk) and small optimizations 983299 (3x) > TRStr

[jira] Issue Comment Edited: (LUCENE-2186) First cut at column-stride fields (index values storage)

[ https://issues.apache.org/jira/browse/LUCENE-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896122#action_12896122 ] Simon Willnauer edited comment on LUCENE-2186 at 8/7/10 1:09 PM: ---

[jira] Resolved: (SOLR-2030) FVH: use Encoder, remove MultiColored*FragmentsBuilder

[ https://issues.apache.org/jira/browse/SOLR-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Sekiguchi resolved SOLR-2030. -- Resolution: Fixed trunk: Committed revision 983212, 983216, 983243. branch_3x: Committed revisio

[jira] Updated: (LUCENE-1183) TRStringDistance uses way too much memory (with patch)

[ https://issues.apache.org/jira/browse/LUCENE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-1183: Attachment: LUCENE-1183_3x.patch while I'm here, here is a little patch for 3x_branch to eliminate

[jira] Updated: (LUCENE-1183) TRStringDistance uses way too much memory (with patch)

[ https://issues.apache.org/jira/browse/LUCENE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-1183: Attachment: LUCENE-1183.patch here is the patch for FuzzyTermsEnum in trunk > TRStringDistance us

[jira] Commented: (SOLR-945) JSON update handler

[ https://issues.apache.org/jira/browse/SOLR-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896254#action_12896254 ] Yonik Seeley commented on SOLR-945: --- OK, I just backported this to the 3x branch. > JSON u

[jira] Reopened: (LUCENE-1183) TRStringDistance uses way too much memory (with patch)

[ https://issues.apache.org/jira/browse/LUCENE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir reopened LUCENE-1183: - Assignee: Robert Muir (was: Otis Gospodnetic) these improvements only made it into fuzzyTERMe

[jira] Commented: (SOLR-2032) Map-viewer demo of SolrSpatial test data

[ https://issues.apache.org/jira/browse/SOLR-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896251#action_12896251 ] Uwe Schindler commented on SOLR-2032: - Why not simply provide the demo using Google Maps

Re: Compound types and internal fields

On Sat, Aug 7, 2010 at 3:33 AM, Lance Norskog wrote: > I have discovered something: if you declare a PointType the subfields > exist and are addressable. If you fill in the subfields directly they > appear in search results, but the parent Point does not. I did this > because my input data has lat

Compound types and internal fields

I have discovered something: if you declare a PointType the subfields exist and are addressable. If you fill in the subfields directly they appear in search results, but the parent Point does not. I did this because my input data has lat/long as separate fields. I have not tested spatial queries, f

[jira] Commented: (SOLR-2032) Map-viewer demo of SolrSpatial test data

[ https://issues.apache.org/jira/browse/SOLR-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896233#action_12896233 ] Lance Norskog commented on SOLR-2032: - We will also need an official Solr ruling about h