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
On Tue, Mar 24, 2015 at 8:14 PM, danush...@wso2.com wrote:
I think same behavior is there in APIM too. They have the API list and
separate list called Recently added. To get recently added to API list
takes few seconds. Can’t we implement similar thing here?
I don't see an issue to fix in
I think same behavior is there in APIM too. They have the API list and separate
list called Recently added. To get recently added to API list takes few
seconds. Can’t we implement similar thing here?
Thanks Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile :
Hi Ajith
What I was pointing out was this could be a fix in our side (AF). Sorry if
I mislead you.
Thanks Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
On Mar 25, 2015 6:11 AM, Ajith Vitharana aji...@wso2.com wrote:
On Tue, Mar 24, 2015 at
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
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
Hi,
We should not make architectural decision fearing a 29 hour data migration
:).
@Chandana and Greg team - If you guys say this is a fixed thing and cannot
be fixed, we'll give priority to our Runtime version database and move
ahead. :)
We'll still keep meta data in registry.
Punnadi and AF
Hi,
I wasn't suggesting to index the resource as soon as it is created, but
rather whether it is possible to fix the 10 second delay that we have to
introduce between creating and reading.
artifactManager.createResource()
//wait 10 seconds --- This is a problem
Hi Dimuthu,
As explained by Ajith as well, this is the expected behavior. However, you
can optimize your indexing related parameters (indexingFrequencyInSeconds,
etc.) according to your requirements and available resources.
Regards,
Chandana
On Wed, Mar 25, 2015 at 10:51 AM, Dimuthu Leelarathne
Hi,
On Wed, Mar 25, 2015 at 5:21 AM, Dimuthu Leelarathne dimut...@wso2.com
wrote:
Hi,
We should not make architectural decision fearing a 29 hour data migration
:).
@Chandana and Greg team - If you guys say this is a fixed thing and cannot
be fixed, we'll give priority to our Runtime
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
11 matches
Mail list logo
