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

Lucene/Solr QA commented on SOLR-7530:
--------------------------------------

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
|| || || || {color:brown} master Compile Tests {color} ||
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} Release audit (RAT) {color} | 
{color:green}  0m  5s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} Validate source patterns {color} | 
{color:green}  0m  5s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} Validate ref guide {color} | 
{color:green}  0m  5s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:black}{color} | {color:black} {color} | {color:black}  1m 38s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | SOLR-7530 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12972112/SOLR-7530.patch |
| Optional Tests |  ratsources  validatesourcepatterns  validaterefguide  |
| uname | Linux lucene1-us-west 4.4.0-137-generic #163~14.04.1-Ubuntu SMP Mon 
Sep 24 17:14:57 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | ant |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-SOLR-Build/sourcedir/dev-tools/test-patch/lucene-solr-yetus-personality.sh
 |
| git revision | master / 2e468ab |
| ant | version: Apache Ant(TM) version 1.9.3 compiled on July 24 2018 |
| modules | C: solr/solr-ref-guide U: solr/solr-ref-guide |
| Console output | 
https://builds.apache.org/job/PreCommit-SOLR-Build/444/console |
| Powered by | Apache Yetus 0.7.0   http://yetus.apache.org |


This message was automatically generated.



> Wrong JSON response using Terms Component with distrib=true
> -----------------------------------------------------------
>
>                 Key: SOLR-7530
>                 URL: https://issues.apache.org/jira/browse/SOLR-7530
>             Project: Solr
>          Issue Type: Bug
>          Components: Response Writers, SearchComponents - other, SolrCloud
>    Affects Versions: 4.9
>            Reporter: Raúl Grande
>            Assignee: Mikhail Khludnev
>            Priority: Major
>             Fix For: master (9.0)
>
>         Attachments: SOLR-7530.patch, SOLR-7530.patch, SOLR-7530.patch, 
> SOLR-7530.patch, SOLR-7530.patch, SOLR-7530.patch, SOLR-7530.patch
>
>
> When using TermsComponent in SolrCloud there are differences in the JSON 
> response if parameter distrib is true or false. If distrib=true JSON is not 
> well formed (please note at the [ ] marks)
> JSON Response when distrib=false. Correct response:
> {"responseHeader":{ 
>               "status":0, 
>               "QTime":3
> }, 
> "terms":{ 
> "FileType":
> [ 
>                       "EMAIL",20060, 
>                       "PDF",7051, 
>                       "IMAGE",5108, 
>                       "OFFICE",4912, 
>                       "TXT",4405, 
>                       "OFFICE_EXCEL",4122, 
>                       "OFFICE_WORD",2468
>               ]
> } } 
> JSON Response when distrib=true. Incorrect response:
> { 
> "responseHeader":{
>               "status":0, 
>               "QTime":94
> }, 
> "terms":{ 
> "FileType":{ 
>                       "EMAIL":31923, 
>                       "PDF":11545, 
>                       "IMAGE":9807, 
>                       "OFFICE_EXCEL":8195, 
>                       "OFFICE":5147, 
>                       "OFFICE_WORD":4820, 
>                       "TIFF":1156, 
>                       "XML":851, 
>                       "HTML":821, 
>                       "RTF":303
>               } 
> } } 



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