Re: Cassandra basic setup

2016-11-30 Thread Igor Rudyak
Regarding *cassandra-bootstrap.sh *and* ignite-bootstrap.sh* current documentation is up to date. These scripts are not automatically updated during release packaging process, according to the documentation (item 5 of *Configuration Details* section,

Re: Cassandra basic setup

2016-11-30 Thread Denis Magda
Cross-posting to the dev list. Igor R., is this something that has to be fixed for 1.8 as well? The community is planning to send the new release for vote by the end of Friday, could you look into this issue by that time? — Denis > On Nov 30, 2016, at 3:00 AM, Riccardo Iacomini

Re: Cassandra basic setup

2016-11-30 Thread Riccardo Iacomini
Hi Igor, I would like to highlight to you another discrepancy I noticed while trying to build the cassandra/ignite/ganglia cluster test in AWS using the provided framework. I've build Ignite 1.7 from source, but the version hard-coded for the modules in the *cassandra-bootstrap.sh *and*

Re: Cassandra basic setup

2016-11-29 Thread Igor Rudyak
Ok, thanks for the info. Igor On Tue, Nov 29, 2016 at 12:56 PM, Denis Magda wrote: > Igor, > > The documentation has been moved to the new integrations related site > https://apacheignite-mix.readme.io/docs/ignite-with-apache-cassandra > > You’re free to update it there. > >

Re: Cassandra basic setup

2016-11-29 Thread Denis Magda
Igor, The documentation has been moved to the new integrations related site https://apacheignite-mix.readme.io/docs/ignite-with-apache-cassandra You’re free to update it there. — Denis > On Nov 29, 2016, at 11:49 AM, Denis

Re: Cassandra basic setup

2016-11-29 Thread Denis Magda
Igor, Please hold on for a while. I’ve just started moving all the integrations related documentation to a new domain. I’ll let you know when it’s safe to update the doc. — Denis > On Nov 29, 2016, at 10:46 AM, Igor Rudyak wrote: > > Hi Riccardo, > > Thanks for noticing

Re: Cassandra basic setup

2016-11-29 Thread Igor Rudyak
Hi Riccardo, Thanks for noticing this. There were number of refactorings done and it looks like we need to update the documentation. I'll update the documentation for the module. Igor On Tue, Nov 29, 2016 at 9:26 AM, Denis Magda wrote: > Igor, > > Would you mind looking

Re: Cassandra basic setup

2016-11-29 Thread Denis Magda
Igor, Would you mind looking through the documentation and updating it whenever is needed? — Denis > On Nov 29, 2016, at 1:58 AM, Riccardo Iacomini > wrote: > > Hi Igor, > I finally discovered what was causing the issue. The example provided >

Re: Cassandra basic setup

2016-11-29 Thread Riccardo Iacomini
Hi Igor, I finally discovered what was causing the issue. The example provided in the Ignite documentation page has a subtle difference in the package structure of several classes, for example:

Re: Cassandra basic setup

2016-11-28 Thread Igor Rudyak
If you are using ignite.sh it should be fine. Igor On Nov 28, 2016 8:29 AM, "Riccardo Iacomini" wrote: > I will try. Yes I am using the ignite.sh command. Any drawbacks? > > Il 28 nov 2016 5:26 PM, "Igor Rudyak" ha scritto: > > Try to check

Re: Cassandra basic setup

2016-11-28 Thread Igor Rudyak
Try to check your classpath. Find ignite process usig something like ps -es | grep Ignite and check java command used to launch ignite. By the way, how you launching Ignite? Do you use ignite.sh script for this? Igor On Nov 28, 2016 8:05 AM, "Riccardo Iacomini"

Re: Cassandra basic setup

2016-11-28 Thread Riccardo Iacomini
Hi Igor, I tried your suggestion, but it does find the class. I've also read from the README files that optional modules must be copied into the libs folder: same outcome. I've tried also the docker image, adding my configuration xml files to it, and running the image as specified here

Re: Cassandra basic setup

2016-11-27 Thread Igor Rudyak
Try to include required jars into IGNITE_LIBS environment variable. Igor On Thu, Nov 24, 2016 at 5:21 AM, Riccardo Iacomini < riccardo.iacom...@rdslab.com> wrote: > Hi Igor, > thanks for your reply. I've both tried building ignite from source and > removing CassandraAdminCredentials class

Re: Cassandra basic setup

2016-11-24 Thread Riccardo Iacomini
Hi Igor, thanks for your reply. I've both tried building ignite from source and removing CassandraAdminCredentials class specifying username and password in the bean's properties. Anyway, I cannot get it work. Ignite still cannot find the required classes, this time

Re: Cassandra basic setup

2016-11-23 Thread Igor Rudyak
Hi Riccardo, *CassandraAdminCredentials *class is only available in Ignite unit tests sources. If you want to use it you should build Ignite from source code. Such way, it will create *ignite-cassandra-tests-${project.version}.zip* where jar may find jar file containing all the test classes.

Cassandra basic setup

2016-11-23 Thread Riccardo Iacomini
Following the example provided in the docs, I am trying to setup a basic Ignite cluster using Cassandra as persistent store. I've downloaded ignite 1.7 and created the configuration files. Ignite does read them at startup, but I get this error