Hi all, If we are to make use of indexing, we need to check the feasibility to index existing data as well because size of data in cloud setup is huge. However this is a one time task that we can find a solution such as copy the indexed data into server after running indexes offline for dump of live data.
It seems that we need to come up with a aggregated solution of indexed data and non-indexed data(new additions) then removing duplicates etc. We can not depend on retries because we can not assume the time taken to index etc. thank you. On Wed, Mar 25, 2015 at 9:57 AM, Punnadi Gunarathna <punn...@wso2.com> wrote: > Hi Dimuthu, > > So shall I go-ahead with indexing? > > On Tue, Mar 24, 2015 at 10:22 PM, Dimuthu Leelarathne <dimut...@wso2.com> > wrote: > >> Hi Chandana, >> >> Could we get fixes from Registry side for this? >> >> thanks, >> dimuthu >> >> >> On Tue, Mar 24, 2015 at 7:29 PM, Punnadi Gunarathna <punn...@wso2.com> >> wrote: >> >>> Hi All, >>> >>> While fixing a cloud bug which is "AF code tries to retrieve information >>> of irrelevant apps when inside an app" [1] , I found that passing a Map >>> object rather than GenericArtifactFilter object to GenericArtifactManager >>> would solve the problem [2]. >>> When I changed the GenericArtifactFilter object to a Map object [3], it >>> threw some exceptions. With the help of Greg team it was found out that the >>> App Factory resources weren't indexed which result those exceptions. So I >>> indexed the resource [5]. >>> >>> But after applying indexing I'm facing more problems as follows: >>> >>> 1. When an application is created, the 'trunk' created via >>> 'appversion.rxt' will not be returned from getAppVersionRXTFromRegistry >>> method in RxtManager.java until for few seconds (such as 10s), So it >>> requires to implement retry attempts until it returns the version 'trunk' >>> to proceed further in app creation process. >>> 2. When an app version is created, newly created verson will not be >>> returned by the same method mentioned in 1, due to the same reason and it >>> will require some code changes to fix the exceptions introduced later in >>> execution path. >>> >>> Moreover this might be a significant issue in Cloud as well. >>> >>> Please advice whether to keep the old implementation or to godhead with >>> indexing and sort the remaining issues. >>> >>> [1] https://wso2.org/jira/browse/APPFAC-3009 >>> [2][Dev] [Greg] What is the difference between overloaded >>> findGenericArtifacts method in GenericArtifactManager - mail >>> [3] >>> https://github.com/punnadih/product-af/commit/dff7920619d25a134daef8f0134744908ae1e402 >>> [4][Dev][App Fac] Registry resources Indexing issue fixed - mail >>> >>> -- >>> Thanks and Regards, >>> >>> Punnadi Gunarathna >>> Senior Software Engineer, >>> WSO2, Inc.; http://wso2.com <http://wso2> >>> Blog: http://hi-my-world.blogspot.com/ >>> Tel : 94 11 214 5345 >>> Fax :94 11 2145300 >>> >>> >>> >>> <http://lalajisureshika.blogspot.com/> >>> >> >> >> >> -- >> Dimuthu Leelarathne >> Architect & Product Lead of App Factory >> >> WSO2, Inc. (http://wso2.com) >> email: dimut...@wso2.com >> Mobile : 0773661935 >> >> Lean . Enterprise . Middleware >> > > > > -- > Thanks and Regards, > > Punnadi Gunarathna > Senior Software Engineer, > WSO2, Inc.; http://wso2.com <http://wso2> > Blog: http://hi-my-world.blogspot.com/ > Tel : 94 11 214 5345 > Fax :94 11 2145300 > > > > <http://lalajisureshika.blogspot.com/> > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Manjula Rathnayaka Software Engineer WSO2, Inc. Mobile:+94 77 743 1987
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
