Hi Ramith, Next carbon-registry release onwards this will be available with content search feature.
Regards, Chandana On Thu, Sep 10, 2015 at 7:05 PM, Ramith Jayasinghe <[email protected]> wrote: > so whats the conclusion? > will this be included in next kernel version (so all product can use it) > or should we pack this ? > > On Thu, Sep 10, 2015 at 12:38 PM, Sriskandarajah Suhothayan <[email protected] > > wrote: > >> We resonantly encountered an issue in rendering the theme when a new >> tenant is created due to missing indexing config. >> So I think this is common for all products >> >> Suho >> >> On Thu, Sep 10, 2015 at 12:30 PM, KasunG Gajasinghe <[email protected]> >> wrote: >> >>> >>> We can do that if indexing is coming from kernel. @Chandana, is that the >>> case? >>> >>> On Thu, Sep 10, 2015 at 12:28 PM, Sriskandarajah Suhothayan < >>> [email protected]> wrote: >>> >>>> Since the above should be used for all the products, shall we move the >>>> common indexing part to the registry.xml of the kernel (pack that in >>>> the feature). >>>> >>>> Specific products can overwrite that as and when needed. >>>> >>>> WDYT? >>>> >>>> Suho >>>> >>>> On Wed, Sep 9, 2015 at 5:10 PM, Chandana Napagoda <[email protected]> >>>> wrote: >>>> >>>>> >>>>> >>>>> On Wed, Sep 9, 2015 at 2:15 PM, KasunG Gajasinghe <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi Chandana/GReg team, >>>>>> >>>>>> Hi Kasun, >>>>> >>>>> >>>>>> Can we know what indexers needs be enabled in other products? Do we >>>>>> need all the indexers mentioned? >>>>>> >>>>> >>>>> Above indexing configuration should be used for all the products which >>>>> doesn't have a governance aspect. Products which have governance aspect, >>>>> need to use RXT indexers as well. >>>>> >>>>>> >>>>>> BTW, I take it that the indexing happens per instance? How does it >>>>>> work with a mounted registry? >>>>>> >>>>> >>>>> Indexing happens per instance, and it doesn't have a relationship with >>>>> mounting. >>>>> >>>>> Regards, >>>>> Chandana >>>>> >>>>>> >>>>>> Thanks. >>>>>> >>>>>> On Wed, Sep 9, 2015 at 1:18 PM, Niranjan Karunanandham < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi Thusitha, >>>>>>> >>>>>>> If this is required by the registry and the file is coming from the >>>>>>> kernel, shouldn't this change to the registry.xml be sent to the kernel >>>>>>> directly? >>>>>>> >>>>>>> Regards, >>>>>>> Nira >>>>>>> >>>>>>> On Wed, Sep 9, 2015 at 12:31 PM, Thusitha Thilina Dayaratne < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> While doing the testing on AS 5.3.0 RC1 pack we found that registry >>>>>>>> search functionality is not working. The issue was that we pack the >>>>>>>> registry.xml file that is provided by the kernel level and it doesn't >>>>>>>> contain the registry indexing related configurations. >>>>>>>> >>>>>>>> According to the offline chat had with the registry team, we have >>>>>>>> to override the default registry.xml that provided with kernel in >>>>>>>> product >>>>>>>> level. >>>>>>>> >>>>>>>> In AS case we have added following configuration to the >>>>>>>> registry.xml and now registry search functionality works >>>>>>>> >>>>>>>> <indexingConfiguration> >>>>>>>>> <startIndexing>true</startIndexing> >>>>>>>>> <startingDelayInSeconds>35</startingDelayInSeconds> >>>>>>>>> <indexingFrequencyInSeconds>3</indexingFrequencyInSeconds> >>>>>>>>> <!--number of resources submit for given indexing thread >>>>>>>>> --> >>>>>>>>> <batchSize>50</batchSize> >>>>>>>>> <!--number of worker threads for indexing --> >>>>>>>>> <indexerPoolSize>50</indexerPoolSize> >>>>>>>>> <!-- location storing the time the indexing took place--> >>>>>>>>> >>>>>>>>> <lastAccessTimeLocation>/_system/local/repository/components/org.wso2.carbon.registry/indexing/lastaccesstime</lastAccessTimeLocation> >>>>>>>>> <!-- the indexers that implement the indexer interface for >>>>>>>>> a relevant media type/(s) --> >>>>>>>>> <indexers> >>>>>>>>> <indexer >>>>>>>>> class="org.wso2.carbon.registry.indexing.indexer.MSExcelIndexer" >>>>>>>>> mediaTypeRegEx="application/vnd.ms-excel"/> >>>>>>>>> <indexer >>>>>>>>> class="org.wso2.carbon.registry.indexing.indexer.MSPowerpointIndexer" >>>>>>>>> mediaTypeRegEx="application/vnd.ms-powerpoint"/> >>>>>>>>> <indexer >>>>>>>>> class="org.wso2.carbon.registry.indexing.indexer.MSWordIndexer" >>>>>>>>> mediaTypeRegEx="application/msword"/> >>>>>>>>> <indexer >>>>>>>>> class="org.wso2.carbon.registry.indexing.indexer.PDFIndexer" >>>>>>>>> mediaTypeRegEx="application/pdf"/> >>>>>>>>> <indexer >>>>>>>>> class="org.wso2.carbon.registry.indexing.indexer.XMLIndexer" >>>>>>>>> mediaTypeRegEx="application/xml"/> >>>>>>>>> <indexer >>>>>>>>> class="org.wso2.carbon.registry.indexing.indexer.XMLIndexer" >>>>>>>>> mediaTypeRegEx="application/(.)+\+xml"/> >>>>>>>>> <indexer >>>>>>>>> class="org.wso2.carbon.registry.indexing.indexer.PlainTextIndexer" >>>>>>>>> mediaTypeRegEx="application/swagger\+json"/> >>>>>>>>> <indexer >>>>>>>>> class="org.wso2.carbon.registry.indexing.indexer.PlainTextIndexer" >>>>>>>>> mediaTypeRegEx="application/(.)+\+json"/> >>>>>>>>> <indexer >>>>>>>>> class="org.wso2.carbon.registry.indexing.indexer.PlainTextIndexer" >>>>>>>>> mediaTypeRegEx="text/(.)+"/> >>>>>>>>> <indexer >>>>>>>>> class="org.wso2.carbon.registry.indexing.indexer.PlainTextIndexer" >>>>>>>>> mediaTypeRegEx="application/x-javascript"/> >>>>>>>>> </indexers> >>>>>>>>> <exclusions> >>>>>>>>> <exclusion >>>>>>>>> pathRegEx="/_system/config/repository/dashboards/gadgets/swfobject1-5/.*[.]html"/> >>>>>>>>> <exclusion >>>>>>>>> pathRegEx="/_system/local/repository/components/org[.]wso2[.]carbon[.]registry/mount/.*"/> >>>>>>>>> </exclusions> >>>>>>>>> </indexingConfiguration> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> We have 2 options >>>>>>>> >>>>>>>> 1. We can override registry.xml file in product level with >>>>>>>> required config >>>>>>>> 2. We can document that we need to add the necessary config to >>>>>>>> registry.xml in order to make registry functionality work without >>>>>>>> overriding it product level >>>>>>>> >>>>>>>> What would be the better approach? >>>>>>>> >>>>>>>> Thanks >>>>>>>> /Thusitha >>>>>>>> -- >>>>>>>> Thusitha Dayaratne >>>>>>>> Software Engineer >>>>>>>> WSO2 Inc. - lean . enterprise . middleware | wso2.com >>>>>>>> >>>>>>>> Mobile +94712756809 >>>>>>>> Blog alokayasoya.blogspot.com >>>>>>>> About http://about.me/thusithathilina >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Dev mailing list >>>>>>>> [email protected] >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> *Niranjan Karunanandham* >>>>>>> Senior Software Engineer - WSO2 Inc. >>>>>>> WSO2 Inc.: http://www.wso2.com >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Dev mailing list >>>>>>> [email protected] >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Chandana Napagoda* >>>>> Senior Software Engineer >>>>> WSO2 Inc. - http://wso2.org >>>>> >>>>> *Email : [email protected] <[email protected]>**Mobile : >>>>> +94718169299 <%2B94718169299>* >>>>> >>>>> *Blog : http://cnapagoda.blogspot.com >>>>> <http://cnapagoda.blogspot.com>* >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> *S. Suhothayan* >>>> Technical Lead & Team Lead of WSO2 Complex Event Processor >>>> *WSO2 Inc. *http://wso2.com >>>> * <http://wso2.com/>* >>>> lean . enterprise . middleware >>>> >>>> >>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: >>>> http://lk.linkedin.com/in/suhothayan >>>> <http://lk.linkedin.com/in/suhothayan>* >>>> >>> >>> >>> >>> -- >>> >>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. >>> email: kasung AT spamfree wso2.com >>> linked-in: http://lk.linkedin.com/in/gajasinghe >>> blog: http://kasunbg.org >>> >>> >>> >> >> >> >> -- >> >> *S. Suhothayan* >> Technical Lead & Team Lead of WSO2 Complex Event Processor >> *WSO2 Inc. *http://wso2.com >> * <http://wso2.com/>* >> lean . enterprise . middleware >> >> >> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: >> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Ramith Jayasinghe > Technical Lead > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > E: [email protected] > P: +94 777542851 > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Chandana Napagoda* Senior Software Engineer WSO2 Inc. - http://wso2.org *Email : [email protected] <[email protected]>**Mobile : +94718169299* *Blog : http://cnapagoda.blogspot.com <http://cnapagoda.blogspot.com>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
