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

Alessandro Benedetti commented on SOLR-7724:
--------------------------------------------

Hi David,
the new patch is ready but I am fighting against the code styling in IntelliJ.
I am using the official xml file but it seems not covering the spacing rules ( 
http://people.apache.org/~erick/Intellij-Lucene-Codestyle.xml)
Where can I find an exhaustive code style ?
I find even incongruences in the QueryResponse official code ( possible ? )

After I solve the code style I will upload the new fixed patch.

Cheers

> Clustering Component results parsing
> ------------------------------------
>
>                 Key: SOLR-7724
>                 URL: https://issues.apache.org/jira/browse/SOLR-7724
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrJ
>    Affects Versions: 5.2.1
>            Reporter: Alessandro Benedetti
>            Assignee: Dawid Weiss
>            Priority: Minor
>              Labels: clustering, clusters, queryResponse
>         Attachments: SOLR-7724.patch, SOLR-7724.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Currently SolrJ org.apache.solr.client.solrj.response.QueryResponse is not 
> managing clusters coming from the Clustering Component .
> It would be nice to have the clusters properly managed and returned with 
> simply getter methods.
> Current Json :
> "clusters":[{
>       "labels":["label1"],
>       "score":14.067292538482793,
>       "docs":["id1",
>         "id2",
> "id3"]
> },
>     {
>       "labels":["label2"],
>       "score":16.932201244715046,
>       "docs":["id1",
>         "id2",
>         "id3"]}]}
> This will be parsed accordingly .
> Producing an easy to use Java List.
> Clusters



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

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

Reply via email to