Hi Sumedha, You still can continue to use the older filter/search APIs of G-Reg and it does support some-level of pagination too, IINM. However, some of the search queries executed against the new Solr-based search for RXT Assets introduced in G-Reg 4.6.0 does not return results due to some limitations in Solr. We cannot move to the newer version of Solr right away since they have major API changes, and we also need to think about the migration (due to the non-backwards-compatible indexing structure/configuration) overhead etc. Therefore, we have moved that to the next major release of G-Reg due to these reasons. From a Store PoV, there are several options.
1. Continue to the older filter/search functionality which is used in AM. 2. Use the proposed workaround. We cannot generalize this since this requires asset specific indexing logic for it to be useful, but it should work and should also produce much better results. 3. Wait for G-Reg to move to the new Solr version. Given the deadlines, I'd rather pick #1 or #2 rather than pushing for #3. Thanks, Senaka. On Wed, Oct 9, 2013 at 10:29 PM, Sumedha Rubasinghe <[email protected]>wrote: > Senaka, > Search options mentioned by Nuwan were supported in previous API Store & > Publisher. We cannot be breaking this feature we used to support. Wasn't > this captured @ product planning? > > > On Wed, Oct 9, 2013 at 7:37 PM, Nuwan Bandara <[email protected]> wrote: > >> Hi All, >> >> The problem at hand is that we cannot do proper searching with new solar >> based searching which comes with GReg. >> >> Imagine you have a API called "importantBusinessAPI", and if I search for >> "business" keyword this wont pop up in the search results. >> >> Also, >> >> If you have "This is a crappy API for searching" in the api description >> (RXT attribute) and If someone search for "crappy api" keyword this api >> wont show up in the search result either. >> >> Also >> >> If I have a api called "HelloWorld" and if I search for "helloworld" as >> the search keyword, I wont get this api in the search results coz its also >> case sensitive too. >> >> for the fist issue there is a reported bug [1], for a user facing product >> like Enterprise Store this is a critical requirement, and we thought the >> search api is rich enough to accommodate all these cases. >> >> ES RC is going out on 21st Oct, and I would like to have these >> improvements done by that time from the registry side if possible. >> >> Also IFAIK, APIManager Store is also using the same solar based search >> feature, have you guys found any workaround for this ? >> >> Regards, >> /Nuwan >> >> [1] https://wso2.org/jira/browse/REGISTRY-1985 >> >> -- >> *Thanks & Regards, >> >> Nuwan Bandara >> Technical Lead; **WSO2 Inc. * >> *lean . enterprise . middleware | http://wso2.com * >> *blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 214 >> 5345 >> * >> <http://www.nuwanbando.com/> >> > > > > -- > /sumedha > m: +94 773017743 > b : bit.ly/sumedha > -- * <http://us13.wso2con.com/> * * * *Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
