Hi,
On Wed, Jun 20, 2012 at 2:11 PM, Tharindu Mathew wrote:
> If these are copied when the feature is present, then it should be safe.
> You can check on this in a BAM server.
>
Will check with BAM server. The concern is, this should be a generic viewer
and should not rely only on Cassandra Fea
If these are copied when the feature is present, then it should be safe.
You can check on this in a BAM server.
I'm nitpicking here, but a few concerns I believe that should be addressed:
- it seems you have used styles not consistent with the rest of carbon.
Shall we use the standard carbon styl
Hi,
Is it safe to read the configuration from cassandra-component.xml and
cassandra-auth.xml and create the connection object? I can modify to pickup
the
connection properties from those files (if exist ) and make that the
connected one by default.
On Wed, Jun 20, 2012 at 1:01 PM, Tharindu Mathe
Shelan,
Right now we have to configure the feature to connect to the embedded
cassandra itself. We should connect to cassandra without any configuration
if the feature is present (unless config is modified). You should only
modify the configuration if you want to connect to an external cluster.
O
Hi,
I have completed moving Cassandra Explorer as a separate feature (Removed
from Cassandra feature) , and following have been addressed mainly (Which
include some minor bug fixes also).
*Improvements.*
- Complete full numbered pagination for Row view of explorer.
- Search rows by their n
