Activity report on *[JIRA] Bug SKER4757 - NewsEspSearchCommand in 2.17 doesn't work in the same way as it did in 2.16 when using size*
Scarab Link: http://sesat.no/scarab/issues/id/SKER4757 Module: Sesat> Kernel Activity generated by Mick Semb Wever ([EMAIL PROTECTED]) at 05/29/2008 16:25 *Reasons for the changes* - Your description does not make sense. I see nowhere in the 2.16 version that size:>0 is applied to the search. In fact it looks (semi) fixed in 2.17. *Attribute changes* - "Description" set to: "NewsEspSearchCommand in 2.17 doesn't work in the same way as it did in 2.16 when using size:>0 Ex: {code}/search/?q=size:>0&c=mlh{code} This doesn’t work in nuclei(2.17), but it works in prod (2.16): Sesam.dump working(2.16): {code}15:26:13,671 [pool-3-thread-1 [NewsEspSearchCommand] mbe.localhost.se:8080/] (6d09036f-884d-4c98-aca1-ab033093b647) INFO Dump: Query[STRING[sortby=publishedtime], INT[hits=100], STRING[sortdirection=descending], BOOL[qtf_lemmatize=true], STRING[query=filter(haswapurl:1)], STRING[qtpipeline=esp5], INT[offset=0], STRING[sesat:uniqueId=6d09036f-884d-4c98-aca1-ab033093b647], STRING[filter= ]] {code} Sesam.dump not working(2.17): {code}15:40:40,484 [pool-3-thread-1 [NewsEspSearchCommand] mbe.localhost.se:8080/] (478602bb-433d-45ec-937f-47dbac54e355) INFO Dump: Query[STRING[sortby=publishedtime], INT[hits=100], STRING[sortdirection=descending], BOOL[qtf_lemmatize=true], STRING[query=filter(haswapurl:1)], STRING[qtpipeline=esp5], INT[offset=0], STRING[sesat:uniqueId=478602bb-433d-45ec-937f-47dbac54e355], STRING[filter= +size:>0 ]] {code} The difference u can find in the last parameter: Working parameter: STRING[filter= ]] Not working parmeter: STRING[filter= +size:>0 ]] So ... When size:>0 is used u have to set the filter parameter to empty String: query.setParameter(“filter”, “”) " - "Description" set to: "Ex: {code}/search/?q=size:>0&c=mlh{code} This doesn’t work in nuclei(2.17), but it works in prod (2.16): Sesam.dump working(2.16): {code}15:26:13,671 [pool-3-thread-1 [NewsEspSearchCommand] mbe.localhost.se:8080/] (6d09036f-884d-4c98-aca1-ab033093b647) INFO Dump: Query[STRING[sortby=publishedtime], INT[hits=100], STRING[sortdirection=descending], BOOL[qtf_lemmatize=true], STRING[query=filter(haswapurl:1)], STRING[qtpipeline=esp5], INT[offset=0], STRING[sesat:uniqueId=6d09036f-884d-4c98-aca1-ab033093b647], STRING[filter= ]] {code} Sesam.dump not working(2.17): {code}15:40:40,484 [pool-3-thread-1 [NewsEspSearchCommand] mbe.localhost.se:8080/] (478602bb-433d-45ec-937f-47dbac54e355) INFO Dump: Query[STRING[sortby=publishedtime], INT[hits=100], STRING[sortdirection=descending], BOOL[qtf_lemmatize=true], STRING[query=filter(haswapurl:1)], STRING[qtpipeline=esp5], INT[offset=0], STRING[sesat:uniqueId=478602bb-433d-45ec-937f-47dbac54e355], STRING[filter= +size:>0 ]] {code} The difference u can find in the last parameter: Working parameter: {code}STRING[filter= ]]{code} Not working parameter: {code}STRING[filter= +size:>0 ]]{code} So ... When size:>0 is used u have to set the filter parameter to empty String: query.setParameter(“filter”, “”) " - "Summary" changed from "NewsEspSearchCommand in 2.17 doesn't work in the same way as it did in 2.16 when using size" to "NewsEspSearchCommand in 2.17 doesn't work in the same way as it did in 2.16 when using size:>0" - "Resolution" set to "Won't Fix" - "Description" set to: "NewsEspSearchCommand in 2.17 doesn't work in the same way as it did in 2.16 when using size:>0 The difference between 2.17 and 2.16 u can find in the filter parameter: Working parameter: filter= (2.16) Not working parmeter: filter= +size:>0 (2.17) So ... When size:>0 is used u have to set the filter parameter to empty String: query.setParameter(“filter”, “”) see attachment for more details.... " - "Description" set to: "Ex: {code}/search/?q=size:>0&c=mlh{code} This doesn’t work in nuclei(2.17), but it works in prod (2.16): Sesam.dump working(2.16): {code}15:26:13,671 [pool-3-thread-1 [NewsEspSearchCommand] mbe.localhost.se:8080/] (6d09036f-884d-4c98-aca1-ab033093b647) INFO Dump: Query[STRING[sortby=publishedtime], INT[hits=100], STRING[sortdirection=descending], BOOL[qtf_lemmatize=true], STRING[query=filter(haswapurl:1)], STRING[qtpipeline=esp5], INT[offset=0], STRING[sesat:uniqueId=6d09036f-884d-4c98-aca1-ab033093b647], STRING[filter= ]] {code} Sesam.dump not working(2.17): {code}15:40:40,484 [pool-3-thread-1 [NewsEspSearchCommand] mbe.localhost.se:8080/] (478602bb-433d-45ec-937f-47dbac54e355) INFO Dump: Query[STRING[sortby=publishedtime], INT[hits=100], STRING[sortdirection=descending], BOOL[qtf_lemmatize=true], STRING[query=filter(haswapurl:1)], STRING[qtpipeline=esp5], INT[offset=0], STRING[sesat:uniqueId=478602bb-433d-45ec-937f-47dbac54e355], STRING[filter= +size:>0 ]] {code} The difference u can find in the last parameter: Working parameter: STRING[filter= ]] Not working parmeter: STRING[filter= +size:>0 ]] So ... When size:>0 is used u have to set the filter parameter to empty String: query.setParameter(“filter”, “”) " ------------------------------------------------------------------------------- *Associated information changes* - Attachment "scarabissue.txt" deleted from the database. -------------------------------------------------------------------------------
_______________________________________________ Kernel-issues mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-issues
