Hi all, We happened to take a look @ the REG_LOG table. There is a separate ID which is used for the primary key. However, this ID is not exposed from the APIs. Therefore, if we are to use something other than the timestamp, then we'll have to do an API change. So, we decided to report a JIRA (Ajith will do that), and fix it for an upcoming release. In the meantime, we'll have to document the limitation. Shelan I think that's the only thing you missed out. I believe that we can safely mark the redmine issue as closed provided that the integration tests are covering good ground. Ajith please have a look into that.
Thanks, Senaka. On Thu, Aug 8, 2013 at 5:31 PM, Shelan Perera <[email protected]> wrote: > Solr integration / scalability > > Clock resolution does not happen for same time activity logging. > > Possibility of using an counter to solve the problem with missing > activities for same time stamp. But not advisable due to data migration > with the schema changes. > > Possibility of running Solr as an external server > > Please add if there is anything missing. > > When you run the performance test , Get not only the average but look for > serious deviations/spikes etc. > > Thanks > > -- > *Shelan Perera* > > Senior Software Engineer > ** > Integration Technology Group > *WSO2, Inc. : wso2.com* > lean.enterprise.middleware. > > *Blog* : blog.shelan.org > *Linked-i*n : http://www.linkedin.com/pub/shelan-perera/a/194/465 > *Twitter* : https://twitter.com/#!/shelan > > *Mobile* : +94 772 604 402 > > -- * <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
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
