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

Joel Bernstein commented on SOLR-12884:
---------------------------------------

I think you would want to sample:
{code:java}
let (a=random(MyCollection, q="*:*", fl="myWordCount_l", rows=100000),
     b=col(a, myWordCount_l),
     c=freqTable(b)){code}
And if you wanted a step function I think you could probably use the *hist* 
function with a set number of bins:
{code:java}
let (a=random(MyCollection, q="*:*", fl="myWordCount_l", rows=100000),
     b=col(a, myWordCount_l),
     c=hist(b, 11)){code}

> Admin UI, admin/luke and *Point fields
> --------------------------------------
>
>                 Key: SOLR-12884
>                 URL: https://issues.apache.org/jira/browse/SOLR-12884
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: master (8.0)
>            Reporter: Erick Erickson
>            Priority: Major
>
> One of the conference attendees noted that you go to the schema browser and 
> click on, say, a pint field, then click "load term info", nothing is shown.
> admin/luke similarly doesn't show much interesting, here's the response for a 
> pint .vs. a tint field:
> "popularity":\{ "type":"pint", "schema":"I-SD-----OF------"},
> "popularityt":{ "type":"tint", "schema":"I-S------OF------",
>                        "index":"-TS--------------", "docs":15},
>  
> What, if anything, should we do in these two cases? Since  the points-based 
> numerics don't have terms like Trie* fields, I don't think we _can_ show much 
> more so the above makes sense, it's just jarring to end users and looks like 
> a bug.
> WDYT about putting in some useful information though. Say for the Admin UI 
> for points-based "terms cannot be shown for points-based fields" or some such?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to