[jira] [Commented] (SOLR-4963) Schema Browser does not report stats properly on TrieDateField

2016-07-30 Thread Thomas Murphy (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400847#comment-15400847
 ] 

Thomas Murphy commented on SOLR-4963:
-

Alexandre, go ahead. I haven't touched this since August 2013.

> Schema Browser does not report stats properly on TrieDateField
> --
>
> Key: SOLR-4963
> URL: https://issues.apache.org/jira/browse/SOLR-4963
> Project: Solr
>  Issue Type: Bug
>  Components: web gui
>Affects Versions: 4.3
> Environment: Customized single-core Solr from example running in 
> default Jetty server.
> Apple Inc. Java HotSpot(TM) 64-Bit Server VM (1.6.0_51 20.51-b01-456)
>Reporter: Thomas Murphy
>Priority: Minor
> Attachments: luke-date.json, solr-admin-query-facet-date.png, 
> solr-admin-schema-browser-date.png
>
>
> Loading documents into a schema with a TrieDateField and viewing that field 
> in the Schema Browser has distinctly wrong information displayed. Encountered 
> using psudo-randomly generated data. 



--
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] [Created] (SOLR-5058) org.apache.solr.update.PeerSync Logging Warning Typo

2013-07-22 Thread Thomas Murphy (JIRA) 
Thomas Murphy created SOLR-5058:
---

 Summary: org.apache.solr.update.PeerSync Logging Warning Typo
 Key: SOLR-5058
 URL: https://issues.apache.org/jira/browse/SOLR-5058
 Project: Solr
  Issue Type: Bug
Affects Versions: 4.3
Reporter: Thomas Murphy
Priority: Trivial


Log entry appears on Solr Admin Logging interface:
WARNPeerSyncno frame of reference to tell of we've missed updates

There is a typo, this looks like it should read "to tell if we've"

PeerSync expands to org.apache.solr.update.PeerSync

--
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-5047) Color Shard/Collection Graph Nodes Based on Child Node Statuses

2013-07-18 Thread Thomas Murphy (JIRA) 
Thomas Murphy created SOLR-5047:
---

 Summary: Color Shard/Collection Graph Nodes Based on Child Node 
Statuses
 Key: SOLR-5047
 URL: https://issues.apache.org/jira/browse/SOLR-5047
 Project: Solr
  Issue Type: Improvement
  Components: web gui
Reporter: Thomas Murphy
Priority: Trivial


In the Solr Admin UI, only the leaf (individual core) nodes have colored 
statuses, leaving collections and shards as no-context nodes. Having status 
information for collections and shards would improve the ability for an 
administrator to recognize which collections and shards are influenced by 
server downtime on certain cores.

With increasing severity, the current core statuses are: Active, Recovering, 
Down, Recovery Failed, Gone

The simplest plan:
* shards inherit the best status of their cores, one functioning core of that 
shard implies that the shard is functional
* collections inherit the worst status of their shards, one missing shard 
implies that the collection is not able to access data

More complicated, but accurate, would be appropriate indication of partially 
failed shards and their influence on the total "health" of the collection.

--
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] [Commented] (SOLR-4963) Schema Browser does not report stats properly on TrieDateField

2013-06-27 Thread Thomas Murphy (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694749#comment-13694749
 ] 

Thomas Murphy commented on SOLR-4963:
-

I'm not sure if there is a simple comment that can be added to the schema 
browser that would make this behavior seem more expected. Compared to the term 
splitting behavior that is evident in the schema for various text fields, the 
creation of additional terms in Trie fields just isn't intuitive. While this 
histogram output is accurate according to the details of the field contents, it 
differs greatly in appearance in comparison to tokenized text fields or fields 
that don't process their inputs. Now that I better understand what a Trie field 
does behind the scenes, the apparently incorrect output seems reasonable. 
However, it is impossible to derive much useful distribution information from 
the stats of a Trie field.

It comes down to comprehension of what the schema browser displays and what a 
Trie field adds to the index. Not properly understanding both and their 
relationship made this appear like a bug, with no help from my use of randomly 
generated dates.

> Schema Browser does not report stats properly on TrieDateField
> --
>
> Key: SOLR-4963
> URL: https://issues.apache.org/jira/browse/SOLR-4963
> Project: Solr
>  Issue Type: Bug
>  Components: web gui
>Affects Versions: 4.3
> Environment: Customized single-core Solr from example running in 
> default Jetty server.
> Apple Inc. Java HotSpot(TM) 64-Bit Server VM (1.6.0_51 20.51-b01-456)
>Reporter: Thomas Murphy
>Priority: Minor
> Attachments: luke-date.json, solr-admin-query-facet-date.png, 
> solr-admin-schema-browser-date.png
>
>
> Loading documents into a schema with a TrieDateField and viewing that field 
> in the Schema Browser has distinctly wrong information displayed. Encountered 
> using psudo-randomly generated data. 

--
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] [Commented] (SOLR-4963) Schema Browser does not report stats properly on TrieDateField

2013-06-26 Thread Thomas Murphy (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693943#comment-13693943
 ] 

Thomas Murphy commented on SOLR-4963:
-

If this is expected behavior, then this is not a bug. I guess this is just side 
effect that I wasn't expecting and it has rather extreme looking output when 
analyzed.

> Schema Browser does not report stats properly on TrieDateField
> --
>
> Key: SOLR-4963
> URL: https://issues.apache.org/jira/browse/SOLR-4963
> Project: Solr
>  Issue Type: Bug
>  Components: web gui
>Affects Versions: 4.3
> Environment: Customized single-core Solr from example running in 
> default Jetty server.
> Apple Inc. Java HotSpot(TM) 64-Bit Server VM (1.6.0_51 20.51-b01-456)
>Reporter: Thomas Murphy
>Priority: Minor
> Attachments: luke-date.json, solr-admin-query-facet-date.png, 
> solr-admin-schema-browser-date.png
>
>
> Loading documents into a schema with a TrieDateField and viewing that field 
> in the Schema Browser has distinctly wrong information displayed. Encountered 
> using psudo-randomly generated data. 

--
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] [Comment Edited] (SOLR-4963) Schema Browser does not report stats properly on TrieDateField

2013-06-25 Thread Thomas Murphy (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693371#comment-13693371
 ] 

Thomas Murphy edited comment on SOLR-4963 at 6/25/13 9:08 PM:
--

Outputs of Admin panel on the index where this issue was encountered. The facet 
search indicates that the most frequent "collision" of dates is 2 in the whole 
index.

Output from http://localhost:8983/solr/collection1/admin/luke?wt=json&fl=date
{"responseHeader":{"status":0,"QTime":583},"index":{"numDocs":100,"maxDoc":100,"deletedDocs":0,"version":223,"segmentCount":1,"current":true,"hasDeletions":false,"directory":"org.apache.lucene.store.NIOFSDirectory:org.apache.lucene.store.NIOFSDirectory@/Users/thomas.murphy/Documents/solr-server/solr/collection1/data/index
 
lockFactory=org.apache.lucene.store.NativeFSLockFactory@6e3404f","userData":{"commitTimeMSec":"1372190047886"},"lastModified":"2013-06-25T19:54:07.886Z"},"fields":{"date":{"type":"tdate","schema":"ITS--F--","index":"-TS-","docs":100,"distinct":3988085,"topTerms":["1970-01-01T00:00:00Z",84,"1970-01-01T00:00:00Z",84,"1970-01-01T00:00:00Z",84,"1970-01-01T00:00:00Z",84,"1983-01-25T04:27:40.416Z",64422,"1970-01-01T00:00:00Z",64307,"1974-05-10T17:29:13.472Z",64305,"1989-08-07T06:41:30.624Z",63981,"1972-03-06T08:44:36.736Z",63964,"1980-11-20T19:43:03.68Z",63889],"histogram":["1",3811101,"2",85359,"4",10212,"8",22026,"16",40816,"32",17218,"64",6,"128",0,"256",0,"512",466,"1024",693,"2048",163,"4096",0,"8192",0,"16384",0,"32768",10,"65536",11,"131072",0,"262144",0,"524288",0,"1048576",4]}},"info":{"key":{"I":"Indexed","T":"Tokenized","S":"Stored","D":"DocValues","M":"Multivalued","V":"TermVector
 Stored","o":"Store Offset With TermVector","p":"Store Position With 
TermVector","O":"Omit Norms","F":"Omit Term Frequencies & Positions","P":"Omit 
Positions","H":"Store Offsets with Positions","L":"Lazy","B":"Binary","f":"Sort 
Missing First","l":"Sort Missing Last"},"NOTE":"Document Frequency (df) is not 
updated when a document is marked for deletion.  df values include deleted 
documents."}}


  was (Author: thomasmurphy):
Outputs of Admin panel on the index where this issue was encountered. The 
facet search indicates that the most frequent "collision" of dates is 2 in the 
whole index.
  
> Schema Browser does not report stats properly on TrieDateField
> --
>
> Key: SOLR-4963
> URL: https://issues.apache.org/jira/browse/SOLR-4963
> Project: Solr
>  Issue Type: Bug
>  Components: web gui
>Affects Versions: 4.3
> Environment: Customized single-core Solr from example running in 
> default Jetty server.
> Apple Inc. Java HotSpot(TM) 64-Bit Server VM (1.6.0_51 20.51-b01-456)
>Reporter: Thomas Murphy
>Priority: Minor
> Attachments: solr-admin-query-facet-date.png, 
> solr-admin-schema-browser-date.png
>
>
> Loading documents into a schema with a TrieDateField and viewing that field 
> in the Schema Browser has distinctly wrong information displayed. Encountered 
> using psudo-randomly generated data. 

--
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-4963) Schema Browser does not report stats properly on TrieDateField

2013-06-25 Thread Thomas Murphy (JIRA) 

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

Thomas Murphy updated SOLR-4963:


Environment: 
Customized single-core Solr from example running in default Jetty server.
Apple Inc. Java HotSpot(TM) 64-Bit Server VM (1.6.0_51 20.51-b01-456)

  was:Customized single-core Solr from example running in default Jetty server.


> Schema Browser does not report stats properly on TrieDateField
> --
>
> Key: SOLR-4963
> URL: https://issues.apache.org/jira/browse/SOLR-4963
> Project: Solr
>  Issue Type: Bug
>  Components: web gui
>Affects Versions: 4.3
> Environment: Customized single-core Solr from example running in 
> default Jetty server.
> Apple Inc. Java HotSpot(TM) 64-Bit Server VM (1.6.0_51 20.51-b01-456)
>Reporter: Thomas Murphy
>Priority: Minor
> Attachments: solr-admin-query-facet-date.png, 
> solr-admin-schema-browser-date.png
>
>
> Loading documents into a schema with a TrieDateField and viewing that field 
> in the Schema Browser has distinctly wrong information displayed. Encountered 
> using psudo-randomly generated data. 

--
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-4963) Schema Browser does not report stats properly on TrieDateField

2013-06-25 Thread Thomas Murphy (JIRA) 

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

Thomas Murphy updated SOLR-4963:


Attachment: solr-admin-schema-browser-date.png
solr-admin-query-facet-date.png

Outputs of Admin panel on the index where this issue was encountered. The facet 
search indicates that the most frequent "collision" of dates is 2 in the whole 
index.

> Schema Browser does not report stats properly on TrieDateField
> --
>
> Key: SOLR-4963
> URL: https://issues.apache.org/jira/browse/SOLR-4963
> Project: Solr
>  Issue Type: Bug
>  Components: web gui
>Affects Versions: 4.3
> Environment: Customized single-core Solr from example running in 
> default Jetty server.
>Reporter: Thomas Murphy
>Priority: Minor
> Attachments: solr-admin-query-facet-date.png, 
> solr-admin-schema-browser-date.png
>
>
> Loading documents into a schema with a TrieDateField and viewing that field 
> in the Schema Browser has distinctly wrong information displayed. Encountered 
> using psudo-randomly generated data. 

--
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-4963) Schema Browser does not report stats properly on TrieDateField

2013-06-25 Thread Thomas Murphy (JIRA) 
Thomas Murphy created SOLR-4963:
---

 Summary: Schema Browser does not report stats properly on 
TrieDateField
 Key: SOLR-4963
 URL: https://issues.apache.org/jira/browse/SOLR-4963
 Project: Solr
  Issue Type: Bug
  Components: web gui
Affects Versions: 4.3
 Environment: Customized single-core Solr from example running in 
default Jetty server.
Reporter: Thomas Murphy
Priority: Minor


Loading documents into a schema with a TrieDateField and viewing that field in 
the Schema Browser has distinctly wrong information displayed. Encountered 
using psudo-randomly generated data. 

--
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