[jira] [Created] (SOLR-7600) Many query functions will cast their operands in float and loose precision in the process.

2015-05-27 Thread Daniel Shane (JIRA)
Daniel Shane created SOLR-7600:
--

 Summary: Many query functions will cast their operands in float 
and loose precision in the process.
 Key: SOLR-7600
 URL: https://issues.apache.org/jira/browse/SOLR-7600
 Project: Solr
  Issue Type: Bug
  Components: Server
Affects Versions: 4.10.3
Reporter: Daniel Shane
Priority: Minor


Function Queries like the 'max' function will cast its result to a float value 
even if the source value cannot be converted to floating point without loosing 
precision.

For example, the max() function will convert dates to floats, and in the 
process we loose some precision (milliseconds). This is problematic if we want 
to sort afterwards since we do not have a millisecond precision anymore. I do 
not know if there is a work around short of creating a new set of query 
functions that would take longs / dates / etc... and return the corresponding 
type and name them 'long_max(), date_max() etc...'

I believe it would be more intuitive if functions like max() would return the 
same type as what they got in their argument (assuming they are all of the same 
type). 

max(date, date) should return a date
max(long, long) should return a long



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-2834) AnalysisResponseBase.java doesn't handle org.apache.solr.analysis.HTMLStripCharFilter

2013-07-26 Thread Shane (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721187#comment-13721187
 ] 

Shane commented on SOLR-2834:
-

It is the applicable portion of the query response.  Specifically

  str name=org.apache.solr.analysis.HTMLStripCharFiltertesting 
analysis/str

is a string but AnalysisResponseBase.java is expecting a list.

 AnalysisResponseBase.java doesn't handle 
 org.apache.solr.analysis.HTMLStripCharFilter
 -

 Key: SOLR-2834
 URL: https://issues.apache.org/jira/browse/SOLR-2834
 Project: Solr
  Issue Type: Bug
  Components: clients - java, Schema and Analysis
Affects Versions: 3.4, 3.6, 4.2
Reporter: Shane
Assignee: Shalin Shekhar Mangar
Priority: Blocker
  Labels: patch
 Attachments: AnalysisResponseBase.patch

   Original Estimate: 5m
  Remaining Estimate: 5m

 When using FieldAnalysisRequest.java to analysis a field, a 
 ClassCastExcpetion is thrown if the schema defines the filter 
 org.apache.solr.analysis.HTMLStripCharFilter.  The exception is:
 java.lang.ClassCastException: java.lang.String cannot be cast to 
 java.util.List
at 
 org.apache.solr.client.solrj.response.AnalysisResponseBase.buildPhases(AnalysisResponseBase.java:69)
at 
 org.apache.solr.client.solrj.response.FieldAnalysisResponse.setResponse(FieldAnalysisResponse.java:66)
at 
 org.apache.solr.client.solrj.request.FieldAnalysisRequest.process(FieldAnalysisRequest.java:107)
 My schema definition is:
 fieldType name=text class=solr.TextField positionIncrementGap=100
   analyzer
 charFilter class=solr.HTMLStripCharFilterFactory /
 tokenizer class=solr.StandardTokenizerFactory /
 filter class=solr.StandardFilterFactory /
 filter class=solr.TrimFilterFactory /
 filter class=solr.LowerCaseFilterFactory /
   /analyzer
 /fieldType
 The response is part is:
 lst name=query
   str name=org.apache.solr.analysis.HTMLStripCharFiltertesting 
 analysis/str
   arr name=org.apache.lucene.analysis.standard.StandardTokenizer
 lst...
 A simplistic fix would be to test if the Entry value is an instance of List.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Created] (SOLR-4917) Logging UI Javascript errors

2013-06-11 Thread Shane (JIRA)
Shane created SOLR-4917:
---

 Summary: Logging UI Javascript errors
 Key: SOLR-4917
 URL: https://issues.apache.org/jira/browse/SOLR-4917
 Project: Solr
  Issue Type: Bug
  Components: web gui
Affects Versions: 4.3
Reporter: Shane
 Fix For: 4.3


When logging has not been configured, the logging/level UI throw some 
JavaScript errors.  I submitted a PR via GitHub.  The GitHub patch can be found 
at https://github.com/apache/lucene-solr/pull/10.patch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (SOLR-2834) AnalysisResponseBase.java doesn't handle org.apache.solr.analysis.HTMLStripCharFilter

2013-05-08 Thread Shane (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shane updated SOLR-2834:


Labels: patch  (was: )
  Priority: Blocker  (was: Major)
 Affects Version/s: 4.2
Remaining Estimate: 5m
 Original Estimate: 5m

This is still a confirmed issue in version 4.2 and presumably in 4.3 
(AnalysisResponseBase.java doesn't appear to have changed between version).

 AnalysisResponseBase.java doesn't handle 
 org.apache.solr.analysis.HTMLStripCharFilter
 -

 Key: SOLR-2834
 URL: https://issues.apache.org/jira/browse/SOLR-2834
 Project: Solr
  Issue Type: Bug
  Components: clients - java, Schema and Analysis
Affects Versions: 3.4, 3.6, 4.2
Reporter: Shane
Priority: Blocker
  Labels: patch
 Attachments: AnalysisResponseBase.patch

   Original Estimate: 5m
  Remaining Estimate: 5m

 When using FieldAnalysisRequest.java to analysis a field, a 
 ClassCastExcpetion is thrown if the schema defines the filter 
 org.apache.solr.analysis.HTMLStripCharFilter.  The exception is:
 java.lang.ClassCastException: java.lang.String cannot be cast to 
 java.util.List
at 
 org.apache.solr.client.solrj.response.AnalysisResponseBase.buildPhases(AnalysisResponseBase.java:69)
at 
 org.apache.solr.client.solrj.response.FieldAnalysisResponse.setResponse(FieldAnalysisResponse.java:66)
at 
 org.apache.solr.client.solrj.request.FieldAnalysisRequest.process(FieldAnalysisRequest.java:107)
 My schema definition is:
 fieldType name=text class=solr.TextField positionIncrementGap=100
   analyzer
 charFilter class=solr.HTMLStripCharFilterFactory /
 tokenizer class=solr.StandardTokenizerFactory /
 filter class=solr.StandardFilterFactory /
 filter class=solr.TrimFilterFactory /
 filter class=solr.LowerCaseFilterFactory /
   /analyzer
 /fieldType
 The response is part is:
 lst name=query
   str name=org.apache.solr.analysis.HTMLStripCharFiltertesting 
 analysis/str
   arr name=org.apache.lucene.analysis.standard.StandardTokenizer
 lst...
 A simplistic fix would be to test if the Entry value is an instance of List.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (SOLR-2834) AnalysisResponseBase.java doesn't handle org.apache.solr.analysis.HTMLStripCharFilter

2012-05-08 Thread Shane (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shane updated SOLR-2834:


Affects Version/s: 3.6

 AnalysisResponseBase.java doesn't handle 
 org.apache.solr.analysis.HTMLStripCharFilter
 -

 Key: SOLR-2834
 URL: https://issues.apache.org/jira/browse/SOLR-2834
 Project: Solr
  Issue Type: Bug
  Components: clients - java, Schema and Analysis
Affects Versions: 3.4, 3.6
Reporter: Shane

 When using FieldAnalysisRequest.java to analysis a field, a 
 ClassCastExcpetion is thrown if the schema defines the filter 
 org.apache.solr.analysis.HTMLStripCharFilter.  The exception is:
 java.lang.ClassCastException: java.lang.String cannot be cast to 
 java.util.List
at 
 org.apache.solr.client.solrj.response.AnalysisResponseBase.buildPhases(AnalysisResponseBase.java:69)
at 
 org.apache.solr.client.solrj.response.FieldAnalysisResponse.setResponse(FieldAnalysisResponse.java:66)
at 
 org.apache.solr.client.solrj.request.FieldAnalysisRequest.process(FieldAnalysisRequest.java:107)
 My schema definition is:
 fieldType name=text class=solr.TextField positionIncrementGap=100
   analyzer
 charFilter class=solr.HTMLStripCharFilterFactory /
 tokenizer class=solr.StandardTokenizerFactory /
 filter class=solr.StandardFilterFactory /
 filter class=solr.TrimFilterFactory /
 filter class=solr.LowerCaseFilterFactory /
   /analyzer
 /fieldType
 The response is part is:
 lst name=query
   str name=org.apache.solr.analysis.HTMLStripCharFiltertesting 
 analysis/str
   arr name=org.apache.lucene.analysis.standard.StandardTokenizer
 lst...
 A simplistic fix would be to test if the Entry value is an instance of List.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (SOLR-2834) AnalysisResponseBase.java doesn't handle org.apache.solr.analysis.HTMLStripCharFilter

2012-05-08 Thread Shane (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shane updated SOLR-2834:


Attachment: AnalysisResponseBase.patch

Patch file for fix to check if the Entry value is an instance of List.

 AnalysisResponseBase.java doesn't handle 
 org.apache.solr.analysis.HTMLStripCharFilter
 -

 Key: SOLR-2834
 URL: https://issues.apache.org/jira/browse/SOLR-2834
 Project: Solr
  Issue Type: Bug
  Components: clients - java, Schema and Analysis
Affects Versions: 3.4, 3.6
Reporter: Shane
 Attachments: AnalysisResponseBase.patch


 When using FieldAnalysisRequest.java to analysis a field, a 
 ClassCastExcpetion is thrown if the schema defines the filter 
 org.apache.solr.analysis.HTMLStripCharFilter.  The exception is:
 java.lang.ClassCastException: java.lang.String cannot be cast to 
 java.util.List
at 
 org.apache.solr.client.solrj.response.AnalysisResponseBase.buildPhases(AnalysisResponseBase.java:69)
at 
 org.apache.solr.client.solrj.response.FieldAnalysisResponse.setResponse(FieldAnalysisResponse.java:66)
at 
 org.apache.solr.client.solrj.request.FieldAnalysisRequest.process(FieldAnalysisRequest.java:107)
 My schema definition is:
 fieldType name=text class=solr.TextField positionIncrementGap=100
   analyzer
 charFilter class=solr.HTMLStripCharFilterFactory /
 tokenizer class=solr.StandardTokenizerFactory /
 filter class=solr.StandardFilterFactory /
 filter class=solr.TrimFilterFactory /
 filter class=solr.LowerCaseFilterFactory /
   /analyzer
 /fieldType
 The response is part is:
 lst name=query
   str name=org.apache.solr.analysis.HTMLStripCharFiltertesting 
 analysis/str
   arr name=org.apache.lucene.analysis.standard.StandardTokenizer
 lst...
 A simplistic fix would be to test if the Entry value is an instance of List.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] Updated: (LUCENE-2327) IndexOutOfBoundsException in FieldInfos.java

2010-03-18 Thread Shane (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shane updated LUCENE-2327:
--

Attachment: CheckIndex.txt

CheckIndex output generated by Luke v1.0.0.

 IndexOutOfBoundsException in FieldInfos.java
 

 Key: LUCENE-2327
 URL: https://issues.apache.org/jira/browse/LUCENE-2327
 Project: Lucene - Java
  Issue Type: Bug
  Components: Index
Affects Versions: 3.0.1
 Environment: Fedora 12
Reporter: Shane
Priority: Minor
 Attachments: CheckIndex.txt


 When retrieving the scoreDocs from a multisearcher, the following exception 
 is thrown:
 java.lang.IndexOutOfBoundsException: Index: 52, Size: 4
 at java.util.ArrayList.rangeCheck(ArrayList.java:571)
 at java.util.ArrayList.get(ArrayList.java:349)
 at org.apache.lucene.index.FieldInfos.fieldInfo(FieldInfos.java:285)
 at org.apache.lucene.index.FieldInfos.fieldName(FieldInfos.java:274)
 at org.apache.lucene.index.TermBuffer.read(TermBuffer.java:86)
 at 
 org.apache.lucene.index.SegmentTermEnum.next(SegmentTermEnum.java:131)
 at 
 org.apache.lucene.index.SegmentTermEnum.scanTo(SegmentTermEnum.java:162)
 at 
 org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:232)
 at 
 org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:179)
 at 
 org.apache.lucene.index.SegmentReader.docFreq(SegmentReader.java:911)
 at 
 org.apache.lucene.index.DirectoryReader.docFreq(DirectoryReader.java:644)
 The error is caused when the fieldNumber passed to FieldInfos.fieldInfo() is 
 greater than the size of array list containing the FieldInfo values.  I am 
 not sure what the field number represents or why it would be larger than the 
 array list's size.  The quick fix would be to validate the bounds but there 
 may be a bigger underlying problem.  The issue does appear to be directly 
 related to LUCENE-939.  I've only been able to duplicate this in my 
 production environment and so can't give a good test case.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Commented: (LUCENE-2327) IndexOutOfBoundsException in FieldInfos.java

2010-03-18 Thread Shane (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846912#action_12846912
 ] 

Shane commented on LUCENE-2327:
---

The index is relatively old and doesn't appear to have been modified for a 
number of years.  I can't say for certain about prior exceptions.  If the 
CheckIndex results provides any more details, then great.  Regardless, I'm 
willing to chalk this up to a system specific error and close the ticket.  I 
was able to fix the index using Luke.

 IndexOutOfBoundsException in FieldInfos.java
 

 Key: LUCENE-2327
 URL: https://issues.apache.org/jira/browse/LUCENE-2327
 Project: Lucene - Java
  Issue Type: Bug
  Components: Index
Affects Versions: 3.0.1
 Environment: Fedora 12
Reporter: Shane
Priority: Minor
 Attachments: CheckIndex.txt


 When retrieving the scoreDocs from a multisearcher, the following exception 
 is thrown:
 java.lang.IndexOutOfBoundsException: Index: 52, Size: 4
 at java.util.ArrayList.rangeCheck(ArrayList.java:571)
 at java.util.ArrayList.get(ArrayList.java:349)
 at org.apache.lucene.index.FieldInfos.fieldInfo(FieldInfos.java:285)
 at org.apache.lucene.index.FieldInfos.fieldName(FieldInfos.java:274)
 at org.apache.lucene.index.TermBuffer.read(TermBuffer.java:86)
 at 
 org.apache.lucene.index.SegmentTermEnum.next(SegmentTermEnum.java:131)
 at 
 org.apache.lucene.index.SegmentTermEnum.scanTo(SegmentTermEnum.java:162)
 at 
 org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:232)
 at 
 org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:179)
 at 
 org.apache.lucene.index.SegmentReader.docFreq(SegmentReader.java:911)
 at 
 org.apache.lucene.index.DirectoryReader.docFreq(DirectoryReader.java:644)
 The error is caused when the fieldNumber passed to FieldInfos.fieldInfo() is 
 greater than the size of array list containing the FieldInfo values.  I am 
 not sure what the field number represents or why it would be larger than the 
 array list's size.  The quick fix would be to validate the bounds but there 
 may be a bigger underlying problem.  The issue does appear to be directly 
 related to LUCENE-939.  I've only been able to duplicate this in my 
 production environment and so can't give a good test case.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Commented: (LUCENE-2327) IndexOutOfBoundsException in FieldInfos.java

2010-03-18 Thread Shane (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846954#action_12846954
 ] 

Shane commented on LUCENE-2327:
---

I believe at the time we were storing on a NAS via NFS.  If my memory serves me 
well, there were known issues with running Lucene over NFS at the time.   We 
were experiencing issues with the file system at the time so have since moved 
to a different architecture. 

Also, I was aware that the fix drops the segments, but thanks anyway. :)

 IndexOutOfBoundsException in FieldInfos.java
 

 Key: LUCENE-2327
 URL: https://issues.apache.org/jira/browse/LUCENE-2327
 Project: Lucene - Java
  Issue Type: Bug
  Components: Index
Affects Versions: 3.0.1
 Environment: Fedora 12
Reporter: Shane
Priority: Minor
 Attachments: CheckIndex.txt


 When retrieving the scoreDocs from a multisearcher, the following exception 
 is thrown:
 java.lang.IndexOutOfBoundsException: Index: 52, Size: 4
 at java.util.ArrayList.rangeCheck(ArrayList.java:571)
 at java.util.ArrayList.get(ArrayList.java:349)
 at org.apache.lucene.index.FieldInfos.fieldInfo(FieldInfos.java:285)
 at org.apache.lucene.index.FieldInfos.fieldName(FieldInfos.java:274)
 at org.apache.lucene.index.TermBuffer.read(TermBuffer.java:86)
 at 
 org.apache.lucene.index.SegmentTermEnum.next(SegmentTermEnum.java:131)
 at 
 org.apache.lucene.index.SegmentTermEnum.scanTo(SegmentTermEnum.java:162)
 at 
 org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:232)
 at 
 org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:179)
 at 
 org.apache.lucene.index.SegmentReader.docFreq(SegmentReader.java:911)
 at 
 org.apache.lucene.index.DirectoryReader.docFreq(DirectoryReader.java:644)
 The error is caused when the fieldNumber passed to FieldInfos.fieldInfo() is 
 greater than the size of array list containing the FieldInfo values.  I am 
 not sure what the field number represents or why it would be larger than the 
 array list's size.  The quick fix would be to validate the bounds but there 
 may be a bigger underlying problem.  The issue does appear to be directly 
 related to LUCENE-939.  I've only been able to duplicate this in my 
 production environment and so can't give a good test case.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org



[jira] Created: (LUCENE-2327) IndexOutOfBoundsException in FieldInfos.java

2010-03-17 Thread Shane (JIRA)
IndexOutOfBoundsException in FieldInfos.java


 Key: LUCENE-2327
 URL: https://issues.apache.org/jira/browse/LUCENE-2327
 Project: Lucene - Java
  Issue Type: Bug
  Components: Index
Affects Versions: 3.0.1
 Environment: Fedora 12
Reporter: Shane
Priority: Minor


When retrieving the scoreDocs from a multisearcher, the following exception is 
thrown:

java.lang.IndexOutOfBoundsException: Index: 52, Size: 4
at java.util.ArrayList.rangeCheck(ArrayList.java:571)
at java.util.ArrayList.get(ArrayList.java:349)
at org.apache.lucene.index.FieldInfos.fieldInfo(FieldInfos.java:285)
at org.apache.lucene.index.FieldInfos.fieldName(FieldInfos.java:274)
at org.apache.lucene.index.TermBuffer.read(TermBuffer.java:86)
at 
org.apache.lucene.index.SegmentTermEnum.next(SegmentTermEnum.java:131)
at 
org.apache.lucene.index.SegmentTermEnum.scanTo(SegmentTermEnum.java:162)
at org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:232)
at org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:179)
at org.apache.lucene.index.SegmentReader.docFreq(SegmentReader.java:911)
at 
org.apache.lucene.index.DirectoryReader.docFreq(DirectoryReader.java:644)

The error is caused when the fieldNumber passed to FieldInfos.fieldInfo() is 
greater than the size of array list containing the FieldInfo values.  I am not 
sure what the field number represents or why it would be larger than the array 
list's size.  The quick fix would be to validate the bounds but there may be a 
bigger underlying problem.  The issue does appear to be directly related to 
LUCENE-939.  I've only been able to duplicate this in my production environment 
and so can't give a good test case.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org