from:"Riccardo Iacomini"

Ignite Info

2017-07-07 Thread Riccardo Iacomini

Hello,
I would like to ask a few questions:

   - Will a local file system persistence strategy be available in future
   releases of Ignite?

   - Using the write-behind mode, will operations on the cache still be
   mapped 1 on 1 on the underlying persistence system, in my specific case,
   Cassandra?

   Expanding on this, multiple operations on the same cache key will be all
   executed (in batch) when the write is triggered, or only the last version
   will be written?


Best

Riccardo Iacomini


*RDSLab*

Configuring SQL queries - ClassNotFoundException: Unknown pair

2017-06-26 Thread Riccardo Iacomini

.cache.database.tree.BPlusTree.invokeDown(BPlusTree.java:1696)*
> * at
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.invoke(BPlusTree.java:1585)*
> * ... 37 more*
> * Caused by: java.lang.ClassNotFoundException: Unknown pair [platformId=0,
> typeId=-901099322]*
> * at
> org.apache.ignite.internal.MarshallerContextImpl.getClassName(MarshallerContextImpl.java:385)*
> * at
> org.apache.ignite.internal.MarshallerContextImpl.getClass(MarshallerContextImpl.java:335)*
> * at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:692)**
> ... 53 more*



Here's my Ignite configuration:


IgniteConfiguration cfg = new IgniteConfiguration();
> CacheConfiguration<String, CloakLeft> configuration = new
> CacheConfiguration();
>
> // Setting Cassandra's data source and persistence settings
> DataSource dataSource = new DataSource();
> dataSource.setContactPoints("172.17.0.2");
> RoundRobinPolicy robinPolicy = new RoundRobinPolicy();
> dataSource.setLoadBalancingPolicy(robinPolicy);
>
> dataSource.setReadConsistency("QUORUM");
> dataSource.setWriteConsistency("QUORUM");
>
> String persistenceSettingsXml = FileUtils.readFileToString(new File(
> persistenceSettingsConfig), "utf-8");
> KeyValuePersistenceSettings persistenceSettings = new
> KeyValuePersistenceSettings(persistenceSettingsXml);
>
> int maxPoolSize = 100;
> CassandraCacheStoreFactory cacheStoreFactory = new
> CassandraCacheStoreFactory();
>
> cacheStoreFactory.setDataSource(dataSource);
> cacheStoreFactory.setPersistenceSettings(persistenceSettings);
>
> // Configuring Ignite cache "cloak"
> configuration.setName("cloak");
> configuration.setCacheStoreFactory(cacheStoreFactory);
> configuration.setWriteThrough(true);
> configuration.setReadThrough(true);
> configuration.setWriteBehindEnabled(true);
>
> // Setting cache types
> configuration.setTypes(String.class, CloakLeft.class);
>
> // Setting and enabling SQL queries
> //configuration.setIndexedTypes(String.class, CloakLeft.class);
> // Configuring fields
> LinkedHashMap<String, String> fields = new LinkedHashMap<String, String>()
> ;
> fields.put("leftmonth", "java.lang.Integer");
> fields.put("leftyear", "java.lang.Integer");
> QueryEntity qe = new QueryEntity("java.lang.String",
> "com.rdslab.cloak.data.CloakLeft");
> qe.setTableName("cloakleft");
> qe.setFields(fields);
> HashSet queryEntities = new HashSet();
> queryEntities.add(qe);
> configuration.setQueryEntities(queryEntities);
>
> cfg.setCacheConfiguration(configuration);
>
> // Configuring ODBC
> OdbcConfiguration odbcConfig = new OdbcConfiguration();
> odbcConfig.setMaxOpenCursors(100);
> cfg.setOdbcConfiguration(odbcConfig);
>
> // Starting Ignite
> Ignite ignite = Ignition.start(cfg);


That's the value type class (I've removed the annotations when trying to
configure the fields using the query entity approach):


> public class CloakLeft implements Serializable {
> @QuerySqlField
> private String username;
>
> @QuerySqlField
> private int leftMonth;
>
> @QuerySqlField
> private int leftYear;
>
> public String getUsername(){ return username; }
> public int getLeftMonth(){ return leftMonth;}
> public int getLeftYear(){ return leftYear; }
> public void setUsername(String value){
> username = value;
> }
> public void setLeftMonth(int value){
> leftMonth = value;
> }
> public void setLeftYear(int value){
> leftYear = value;
> }
> }


Any indication to solve the issue is really appreciated.

Best

Riccardo Iacomini


*RDSLab*

Re: ODBC driver issue

2017-06-15 Thread Riccardo Iacomini

The env command confirmed that the variable was correctly set. I tried to
go over the installation process again, and now I managed to get it
working. I do not actually know the exact reason, but let's say I am happy
with it.

I've now configured a Cassandra backed cache, and wanted to query it using
the odbc driver. Any useful resource about the subject is really
appreciated.

Thank you for your help so far.

Best regards

Riccardo Iacomini


*RDSLab*

On Thu, Jun 15, 2017 at 11:45 AM, Igor Sapego <isap...@gridgain.com> wrote:

> Have you restarted your terminal after that? What does env command show?
> Is it set?
>
> Best Regards,
> Igor
>
> On Wed, Jun 14, 2017 at 6:18 PM, Riccardo Iacomini <
> riccardo.iacom...@rdslab.com> wrote:
>
>> Yes, I've set the env variable, globally in /etc/environment. Just for
>> completeness, I am running Ubuntu 16.04.
>>
>> Best
>>
>> Riccardo Iacomini
>>
>>
>> *RDSLab*
>>
>> On Wed, Jun 14, 2017 at 1:02 PM, Igor Sapego <isap...@gridgain.com>
>> wrote:
>>
>>> Do you set LD_LIBRARY_PATH to /usr/local/lib? If 'yes' then
>>> can you describe in details how you do that? This may help
>>> to identify an issue.
>>>
>>> Best Regards,
>>> Igor
>>>
>>> On Wed, Jun 14, 2017 at 12:30 PM, Riccardo Iacomini <
>>> riccardo.iacom...@rdslab.com> wrote:
>>>
>>>> Hello Igor,
>>>> I double checked the documentation and went over the steps again to be
>>>> sure everything is ok. I tried running your command, that's the output:
>>>>
>>>>  linux-vdso.so.1 =>  (0x7fff75dd6000)
>>>>> libignite-binary-2.0.0.19668.so.0 => 
>>>>> /usr/local/lib/libignite-binary-2.0.0.19668.so.0
>>>>> (0x7f40e5349000)
>>>>> libodbcinst.so.2 => /usr/local/lib/libodbcinst.so.2
>>>>> (0x7f40e5134000)
>>>>> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
>>>>> (0x7f40e4d8a000)
>>>>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f40e49c1000)
>>>>> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
>>>>> (0x7f40e47ab000)
>>>>> libignite-common-2.0.0.19668.so.0 => 
>>>>> /usr/local/lib/libignite-common-2.0.0.19668.so.0
>>>>> (0x7f40e4594000)
>>>>> libltdl.so.7 => /usr/lib/x86_64-linux-gnu/libltdl.so.7
>>>>> (0x7f40e438a000)
>>>>> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>>>>> (0x7f40e416d000)
>>>>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f40e3e63000)
>>>>> /lib64/ld-linux-x86-64.so.2 (0x555643691000)
>>>>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f40e3c5f000)
>>>>
>>>>
>>>>
>>>> however, I still get the same error from python:
>>>>
>>>> *pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open
>>>>> lib 'Apache Ignite' : file not found (0) (SQLDriverConnect)")*
>>>>
>>>>
>>>>
>>>> Best
>>>>
>>>> Riccardo Iacomini
>>>>
>>>>
>>>> *RDSLab*
>>>>
>>>> On Wed, Jun 14, 2017 at 11:10 AM, Igor Sapego <isap...@gridgain.com>
>>>> wrote:
>>>>
>>>>> So, setting LD_LIBRARY_PATH to /usr/local/lib should definetly help.
>>>>> Are you sure your did everything right? Try the following command (in
>>>>> one line):
>>>>> LD_LIBRARY_PATH=/usr/local/lib ldd /usr/local/lib/libignite-odbc.so
>>>>>
>>>>> Best Regards,
>>>>> Igor
>>>>>
>>>>> On Wed, Jun 14, 2017 at 10:15 AM, Riccardo Iacomini <
>>>>> riccardo.iacom...@rdslab.com> wrote:
>>>>>
>>>>>> As asked:
>>>>>>
>>>>>>>
>>>>>>> linux-vdso.so.1 =>  (0x7ffca6776000)
>>>>>>> libignite-binary-2.0.0.19668.so.0 => not found
>>>>>>> libodbcinst.so.2 => /usr/lib/x86_64-linux-gnu/libodbcinst.so.2
>>>>>>> (0x7fb92ead4000)
>>>>>>> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
>>>>>>> (0x7fb92e751000)
>>>>>>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb92e388000)
>>>>>>> libgcc_s.so.

Re: ODBC driver issue

2017-06-14 Thread Riccardo Iacomini

Yes, I've set the env variable, globally in /etc/environment. Just for
completeness, I am running Ubuntu 16.04.

Best

Riccardo Iacomini


*RDSLab*

On Wed, Jun 14, 2017 at 1:02 PM, Igor Sapego <isap...@gridgain.com> wrote:

> Do you set LD_LIBRARY_PATH to /usr/local/lib? If 'yes' then
> can you describe in details how you do that? This may help
> to identify an issue.
>
> Best Regards,
> Igor
>
> On Wed, Jun 14, 2017 at 12:30 PM, Riccardo Iacomini <
> riccardo.iacom...@rdslab.com> wrote:
>
>> Hello Igor,
>> I double checked the documentation and went over the steps again to be
>> sure everything is ok. I tried running your command, that's the output:
>>
>>  linux-vdso.so.1 =>  (0x7fff75dd6000)
>>> libignite-binary-2.0.0.19668.so.0 => 
>>> /usr/local/lib/libignite-binary-2.0.0.19668.so.0
>>> (0x7f40e5349000)
>>> libodbcinst.so.2 => /usr/local/lib/libodbcinst.so.2 (0x7f40e5134000)
>>> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
>>> (0x7f40e4d8a000)
>>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f40e49c1000)
>>> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
>>> (0x7f40e47ab000)
>>> libignite-common-2.0.0.19668.so.0 => 
>>> /usr/local/lib/libignite-common-2.0.0.19668.so.0
>>> (0x7f40e4594000)
>>> libltdl.so.7 => /usr/lib/x86_64-linux-gnu/libltdl.so.7
>>> (0x7f40e438a000)
>>> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>>> (0x7f40e416d000)
>>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f40e3e63000)
>>> /lib64/ld-linux-x86-64.so.2 (0x555643691000)
>>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f40e3c5f000)
>>
>>
>>
>> however, I still get the same error from python:
>>
>> *pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open
>>> lib 'Apache Ignite' : file not found (0) (SQLDriverConnect)")*
>>
>>
>>
>> Best
>>
>> Riccardo Iacomini
>>
>>
>> *RDSLab*
>>
>> On Wed, Jun 14, 2017 at 11:10 AM, Igor Sapego <isap...@gridgain.com>
>> wrote:
>>
>>> So, setting LD_LIBRARY_PATH to /usr/local/lib should definetly help.
>>> Are you sure your did everything right? Try the following command (in
>>> one line):
>>> LD_LIBRARY_PATH=/usr/local/lib ldd /usr/local/lib/libignite-odbc.so
>>>
>>> Best Regards,
>>> Igor
>>>
>>> On Wed, Jun 14, 2017 at 10:15 AM, Riccardo Iacomini <
>>> riccardo.iacom...@rdslab.com> wrote:
>>>
>>>> As asked:
>>>>
>>>>>
>>>>> linux-vdso.so.1 =>  (0x7ffca6776000)
>>>>> libignite-binary-2.0.0.19668.so.0 => not found
>>>>> libodbcinst.so.2 => /usr/lib/x86_64-linux-gnu/libodbcinst.so.2
>>>>> (0x7fb92ead4000)
>>>>> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
>>>>> (0x7fb92e751000)
>>>>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb92e388000)
>>>>> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
>>>>> (0x7fb92e172000)
>>>>> libltdl.so.7 => /usr/lib/x86_64-linux-gnu/libltdl.so.7
>>>>> (0x7fb92df67000)
>>>>> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>>>>> (0x7fb92dd4a000)
>>>>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fb92da41000)
>>>>> /lib64/ld-linux-x86-64.so.2 (0x560f6c5b)
>>>>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fb92d83c000)
>>>>
>>>>
>>>>
>>>> seems like libignite-binary is not found, but if you look at the
>>>> directory listing I previously posted, it should be there.
>>>>
>>>>
>>>>
>>>> Riccardo Iacomini
>>>>
>>>>
>>>> *RDSLab*
>>>>
>>>> On Tue, Jun 13, 2017 at 6:20 PM, Igor Sapego <isap...@gridgain.com>
>>>> wrote:
>>>>
>>>>> Well, try running the following command:
>>>>> ldd /usr/local/lib/libignite-odbc.so
>>>>>
>>>>> This may help us see which library can't be found.
>>>>>
>>>>> Best Regards,
>>>>> Igor
>>>>>
>>>>> On Tue, Jun 13, 2017 at 6:10 PM, Riccardo Iacomini <
>>>>> riccardo.iacom...@rdslab.com&

Re: ODBC driver issue

2017-06-14 Thread Riccardo Iacomini

Hello Igor,
I double checked the documentation and went over the steps again to be sure
everything is ok. I tried running your command, that's the output:

 linux-vdso.so.1 =>  (0x7fff75dd6000)
> libignite-binary-2.0.0.19668.so.0 =>
> /usr/local/lib/libignite-binary-2.0.0.19668.so.0 (0x7f40e5349000)
> libodbcinst.so.2 => /usr/local/lib/libodbcinst.so.2 (0x7f40e5134000)
> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> (0x7f40e4d8a000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f40e49c1000)
> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f40e47ab000)
> libignite-common-2.0.0.19668.so.0 =>
> /usr/local/lib/libignite-common-2.0.0.19668.so.0 (0x7f40e4594000)
> libltdl.so.7 => /usr/lib/x86_64-linux-gnu/libltdl.so.7 (0x7f40e438a000)
> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> (0x7f40e416d000)
> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f40e3e63000)
> /lib64/ld-linux-x86-64.so.2 (0x555643691000)
> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f40e3c5f000)



however, I still get the same error from python:

*pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open lib
> 'Apache Ignite' : file not found (0) (SQLDriverConnect)")*



Best

Riccardo Iacomini


*RDSLab*

On Wed, Jun 14, 2017 at 11:10 AM, Igor Sapego <isap...@gridgain.com> wrote:

> So, setting LD_LIBRARY_PATH to /usr/local/lib should definetly help.
> Are you sure your did everything right? Try the following command (in one
> line):
> LD_LIBRARY_PATH=/usr/local/lib ldd /usr/local/lib/libignite-odbc.so
>
> Best Regards,
> Igor
>
> On Wed, Jun 14, 2017 at 10:15 AM, Riccardo Iacomini <
> riccardo.iacom...@rdslab.com> wrote:
>
>> As asked:
>>
>>>
>>> linux-vdso.so.1 =>  (0x7ffca6776000)
>>> libignite-binary-2.0.0.19668.so.0 => not found
>>> libodbcinst.so.2 => /usr/lib/x86_64-linux-gnu/libodbcinst.so.2
>>> (0x7fb92ead4000)
>>> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
>>> (0x7fb92e751000)
>>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb92e388000)
>>> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
>>> (0x7fb92e172000)
>>> libltdl.so.7 => /usr/lib/x86_64-linux-gnu/libltdl.so.7
>>> (0x7fb92df67000)
>>> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>>> (0x7fb92dd4a000)
>>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fb92da41000)
>>> /lib64/ld-linux-x86-64.so.2 (0x560f6c5b)
>>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fb92d83c000)
>>
>>
>>
>> seems like libignite-binary is not found, but if you look at the
>> directory listing I previously posted, it should be there.
>>
>>
>>
>> Riccardo Iacomini
>>
>>
>> *RDSLab*
>>
>> On Tue, Jun 13, 2017 at 6:20 PM, Igor Sapego <isap...@gridgain.com>
>> wrote:
>>
>>> Well, try running the following command:
>>> ldd /usr/local/lib/libignite-odbc.so
>>>
>>> This may help us see which library can't be found.
>>>
>>> Best Regards,
>>> Igor
>>>
>>> On Tue, Jun 13, 2017 at 6:10 PM, Riccardo Iacomini <
>>> riccardo.iacom...@rdslab.com> wrote:
>>>
>>>> Thank you for the reply Igor,
>>>>
>>>> the error just changed into:
>>>>
>>>> *pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open
>>>>> lib 'Apache Ignite' : file not found (0) (SQLDriverConnect)")*
>>>>
>>>>
>>>>
>>>> The Ignite Driver seems to be installed. Here's my /etc/odbcinst.ini :
>>>>
>>>> [Apache Ignite]
>>>>> Description=Apache Ignite
>>>>> Driver=/usr/local/lib/libignite-odbc.so
>>>>> Setup=/usr/local/lib/libignite-odbc.so
>>>>> DriverODBCVer=03.00
>>>>> FileUsage=0
>>>>> UsageCount=3
>>>>
>>>>
>>>>
>>>>
>>>> Riccardo Iacomini
>>>>
>>>>
>>>> *RDSLab*
>>>>
>>>> On Tue, Jun 13, 2017 at 4:31 PM, Igor Sapego <isap...@gridgain.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Try adding /usr/local/lib/ to LD_LIBRARY_PATH evn variable.
>>>>>
>>>>> Best Regards,
>>>>> Igor
>>>>>
>>>>> On Tue, J

Re: ODBC driver issue

2017-06-14 Thread Riccardo Iacomini

As asked:

>
> linux-vdso.so.1 =>  (0x7ffca6776000)
> libignite-binary-2.0.0.19668.so.0 => not found
> libodbcinst.so.2 => /usr/lib/x86_64-linux-gnu/libodbcinst.so.2
> (0x7fb92ead4000)
> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> (0x7fb92e751000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb92e388000)
> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7fb92e172000)
> libltdl.so.7 => /usr/lib/x86_64-linux-gnu/libltdl.so.7 (0x7fb92df67000)
> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> (0x7fb92dd4a000)
> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fb92da41000)
> /lib64/ld-linux-x86-64.so.2 (0x560f6c5b)
> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fb92d83c000)



seems like libignite-binary is not found, but if you look at the directory
listing I previously posted, it should be there.



Riccardo Iacomini


*RDSLab*

On Tue, Jun 13, 2017 at 6:20 PM, Igor Sapego <isap...@gridgain.com> wrote:

> Well, try running the following command:
> ldd /usr/local/lib/libignite-odbc.so
>
> This may help us see which library can't be found.
>
> Best Regards,
> Igor
>
> On Tue, Jun 13, 2017 at 6:10 PM, Riccardo Iacomini <
> riccardo.iacom...@rdslab.com> wrote:
>
>> Thank you for the reply Igor,
>>
>> the error just changed into:
>>
>> *pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open
>>> lib 'Apache Ignite' : file not found (0) (SQLDriverConnect)")*
>>
>>
>>
>> The Ignite Driver seems to be installed. Here's my /etc/odbcinst.ini :
>>
>> [Apache Ignite]
>>> Description=Apache Ignite
>>> Driver=/usr/local/lib/libignite-odbc.so
>>> Setup=/usr/local/lib/libignite-odbc.so
>>> DriverODBCVer=03.00
>>> FileUsage=0
>>> UsageCount=3
>>
>>
>>
>>
>> Riccardo Iacomini
>>
>>
>> *RDSLab*
>>
>> On Tue, Jun 13, 2017 at 4:31 PM, Igor Sapego <isap...@gridgain.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Try adding /usr/local/lib/ to LD_LIBRARY_PATH evn variable.
>>>
>>> Best Regards,
>>> Igor
>>>
>>> On Tue, Jun 13, 2017 at 4:54 PM, Riccardo Iacomini <
>>> riccardo.iacom...@rdslab.com> wrote:
>>>
>>>> Hello,
>>>> I am trying to access Ignite 2.0 using the ODBC driver. I've followed the
>>>> guide <https://apacheignite.readme.io/docs/odbc-driver>, and tried to
>>>> access Ignite via Python using the pyodbc module:
>>>>
>>>>
>>>>> *import pyodbc**ignite = pyodbc.connect('DRIVER={Apache
>>>>> Ignite};ADDRESS=localhost:10800;CACHE=cache1')*
>>>>
>>>>
>>>> however I get:
>>>>
>>>> *pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open
>>>>> lib '/usr/local/lib/libignite-odbc.so' : file not found (0)
>>>>> (SQLDriverConnect)")*
>>>>
>>>>
>>>> The library is instead located the path; this is the directory listing
>>>> of */usr/local/lib:*
>>>>
>>>> drwxr-xr-x  5 root root 4096 giu 13 15:26 ./
>>>>> drwxr-xr-x 12 root root 4096 nov 22  2016 ../
>>>>> lrwxrwxrwx  1 root root   37 giu 13 15:24
>>>>> libignite-binary-2.0.0.19668.so.0 -> libignite-binary-2.0.0.19668.s
>>>>> o.0.0.0*
>>>>> -rwxr-xr-x  1 root root  1777000 giu 13 15:24
>>>>> libignite-binary-2.0.0.19668.so.0.0.0*
>>>>> -rw-r--r--  1 root root  4617182 giu 13 15:24
>>>>> libignite-binary.a
>>>>> -rwxr-xr-x  1 root root 1089 giu 13 15:24
>>>>> libignite-binary.la*
>>>>> lrwxrwxrwx  1 root root   37 giu 13 15:24
>>>>> libignite-binary.so -> libignite-binary-2.0.0.19668.so.0.0.0*
>>>>> lrwxrwxrwx  1 root root   37 giu 13 15:24
>>>>> libignite-common-2.0.0.19668.so.0 -> libignite-common-2.0.0.19668.s
>>>>> o.0.0.0*
>>>>> -rwxr-xr-x  1 root root   648856 giu 13 15:24
>>>>> libignite-common-2.0.0.19668.so.0.0.0*
>>>>> -rw-r--r--  1 root root  1493756 giu 13 15:24
>>>>> libignite-common.a
>>>>> -rwxr-xr-x  1 root root 1054 giu 13 15:24
>>>>> libignite-common.la*
>>>>> lrwxrwxrwx  1 root root   37 giu 13 15:24
&

Re: ODBC driver issue

2017-06-13 Thread Riccardo Iacomini

Thank you for the reply Igor,

the error just changed into:

*pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open lib
> 'Apache Ignite' : file not found (0) (SQLDriverConnect)")*



The Ignite Driver seems to be installed. Here's my /etc/odbcinst.ini :

[Apache Ignite]
> Description=Apache Ignite
> Driver=/usr/local/lib/libignite-odbc.so
> Setup=/usr/local/lib/libignite-odbc.so
> DriverODBCVer=03.00
> FileUsage=0
> UsageCount=3




Riccardo Iacomini


*RDSLab*

On Tue, Jun 13, 2017 at 4:31 PM, Igor Sapego <isap...@gridgain.com> wrote:

> Hi,
>
> Try adding /usr/local/lib/ to LD_LIBRARY_PATH evn variable.
>
> Best Regards,
> Igor
>
> On Tue, Jun 13, 2017 at 4:54 PM, Riccardo Iacomini <
> riccardo.iacom...@rdslab.com> wrote:
>
>> Hello,
>> I am trying to access Ignite 2.0 using the ODBC driver. I've followed the
>> guide <https://apacheignite.readme.io/docs/odbc-driver>, and tried to
>> access Ignite via Python using the pyodbc module:
>>
>>
>>> *import pyodbc**ignite = pyodbc.connect('DRIVER={Apache
>>> Ignite};ADDRESS=localhost:10800;CACHE=cache1')*
>>
>>
>> however I get:
>>
>> *pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open
>>> lib '/usr/local/lib/libignite-odbc.so' : file not found (0)
>>> (SQLDriverConnect)")*
>>
>>
>> The library is instead located the path; this is the directory listing of
>> */usr/local/lib:*
>>
>> drwxr-xr-x  5 root root 4096 giu 13 15:26 ./
>>> drwxr-xr-x 12 root root 4096 nov 22  2016 ../
>>> lrwxrwxrwx  1 root root   37 giu 13 15:24
>>> libignite-binary-2.0.0.19668.so.0 -> libignite-binary-2.0.0.19668.s
>>> o.0.0.0*
>>> -rwxr-xr-x  1 root root  1777000 giu 13 15:24
>>> libignite-binary-2.0.0.19668.so.0.0.0*
>>> -rw-r--r--  1 root root  4617182 giu 13 15:24 libignite-binary.a
>>> -rwxr-xr-x  1 root root 1089 giu 13 15:24
>>> libignite-binary.la*
>>> lrwxrwxrwx  1 root root   37 giu 13 15:24
>>> libignite-binary.so -> libignite-binary-2.0.0.19668.so.0.0.0*
>>> lrwxrwxrwx  1 root root   37 giu 13 15:24
>>> libignite-common-2.0.0.19668.so.0 -> libignite-common-2.0.0.19668.s
>>> o.0.0.0*
>>> -rwxr-xr-x  1 root root   648856 giu 13 15:24
>>> libignite-common-2.0.0.19668.so.0.0.0*
>>> -rw-r--r--  1 root root  1493756 giu 13 15:24 libignite-common.a
>>> -rwxr-xr-x  1 root root 1054 giu 13 15:24
>>> libignite-common.la*
>>> lrwxrwxrwx  1 root root   37 giu 13 15:24
>>> libignite-common.so -> libignite-common-2.0.0.19668.so.0.0.0*
>>> lrwxrwxrwx  1 root root   35 giu 13 15:24
>>> libignite-odbc-2.0.0.19668.so.0 -> libignite-odbc-2.0.0.19668.so.0.0.0*
>>> -rwxr-xr-x  1 root root  6581160 giu 13 15:24
>>> libignite-odbc-2.0.0.19668.so.0.0.0*
>>> -rw-r--r--  1 root root 18307190 giu 13 15:24 libignite-odbc.a
>>> -rwxr-xr-x  1 root root 1121 giu 13 15:24 libignite-odbc.la*
>>> lrwxrwxrwx  1 root root   35 giu 13 15:24 libignite-odbc.so
>>> -> libignite-odbc-2.0.0.19668.so.0.0.0*
>>> -rw-rw-r--  1 riccardo riccardo 46518354 feb 20 12:53 libntl.a
>>> -rwxr-xr-x  1 root root  966 giu 13 15:26 libodbccr.la*
>>> lrwxrwxrwx  1 root root   18 giu 13 15:26 libodbccr.so ->
>>> libodbccr.so.2.0.0*
>>> lrwxrwxrwx  1 root root   18 giu 13 15:26 libodbccr.so.2 ->
>>> libodbccr.so.2.0.0*
>>> -rwxr-xr-x  1 root root   507264 giu 13 15:26 libodbccr.so.2.0.0*
>>> -rwxr-xr-x  1 root root 1015 giu 13 15:26 libodbcinst.la*
>>> lrwxrwxrwx  1 root root   20 giu 13 15:26 libodbcinst.so ->
>>> libodbcinst.so.2.0.0*
>>> lrwxrwxrwx  1 root root   20 giu 13 15:26 libodbcinst.so.2
>>> -> libodbcinst.so.2.0.0*
>>> -rwxr-xr-x  1 root root   463392 giu 13 15:26
>>> libodbcinst.so.2.0.0*
>>> -rwxr-xr-x  1 root root  991 giu 13 15:26 libodbc.la*
>>> lrwxrwxrwx  1 root root   16 giu 13 15:26 libodbc.so ->
>>> libodbc.so.2.0.0*
>>> lrwxrwxrwx  1 root root   16 giu 13 15:26 libodbc.so.2 ->
>>> libodbc.so.2.0.0*
>>> -rwxr-xr-x  1 root root  2274544 giu 13 15:26 libodbc.so.2.0.0*
>>> drwxrwsr-x  4 root staff4096 nov 29  2016 python2.7/
>>> drwxrwsr-x  3 root staff4096 ott 21  2015 python3.5/
>>> drwxr-xr-x  3 root root 4096 giu 12 23:38 site_ruby/
>>
>>
>> Any suggestion on how to procede?
>>
>> Thank you
>>
>> Riccardo Iacomini
>>
>>
>> *RDSLab*
>>
>
>

Cassandra cache info

2016-12-02 Thread Riccardo Iacomini

I would like to ask some info about the Cassandra integration I could not
find in the documentation.

   - Is there a way one could use ignite cache selectively on one or more
   particular cassandra's tables, and still query all the data using only the
   Ignite driver? I mean, can I set a table simply not to be retained in the
   Ignite cache, or I need to query the data selectively using the Cassandra
   driver or the Ignite driver according to the table to be accessed?

   - Can I configure the size of a cache backed up by a Cassandra table?


   - How are Cassandra's secondary indexes managed under the hood?

In general, I would like to understand if the Cassandra integration is
meant to be used transparently (therefore thinking in terms of Cassandra's
underlying storage), or
once set up the mapping I should think in terms of Ignite cache elements.

Thank you in advance for the information.

Riccardo Iacomini


*RDSLab*

Re: Ignite Cassandra AWS test framework

2016-12-02 Thread Riccardo Iacomini

Thank you Igor,
unfortunately the issue I was referring to is still present in the
documentation. Actually the AWS test deployment section
<https://apacheignite-mix.readme.io/docs/aws-infrastructure-deployment> is
still the same. I also tried running the deployment scripts in AWS without
the *bootstrap/aws/env.sh *which was among the ones missing in the generate
test package, but nothing was going on in the instances. Also, the status
of the process was not updated into the S3 folder as suggested in the
documentation.

Could it be for some reason that I get a test-package from the src code
which does not include the needed files (maybe some build errors)?

Have a nice day

Riccardo Iacomini

*RDSLab*

On Fri, Dec 2, 2016 at 7:23 AM, Igor Rudyak <irud...@gmail.com> wrote:

> Ok guys, just updated the documentation.
>
> Igor
>
> On Thu, Dec 1, 2016 at 4:44 PM, Igor Rudyak <irud...@gmail.com> wrote:
>
>> Hi Riccardo,
>>
>> Thanks for noticing this. That's a documentation issue. There were number
>> of refactorings for Ignite-Cassandra and documentation now is not 100% up
>> to date.
>>
>> Igor
>>
>> On Thu, Dec 1, 2016 at 3:13 PM, Riccardo Iacomini <
>> riccardo.iacom...@rdslab.com> wrote:
>>
>>> Hi Val,
>>>
>>> No, that's not the issue. I would like to follow the AWS
>>> ignite-cassandra framework guide on the documentation, but some files the
>>> documentation says I should modify are not in the test-package after I
>>> build ignite from source.
>>>
>>> Just to be clear, this is the link to the guide I am actually trying to
>>> follow:
>>> https://apacheignite-mix.readme.io/docs/aws-infrastructure-deployment
>>>
>>> Il 01 dic 2016 11:56 PM, "vkulichenko" <valentin.kuliche...@gmail.com>
>>> ha scritto:
>>>
>>> Hi Riccardo,
>>>
>>> Do you mean that you have problems starting Cassandra? If so, I think
>>> it's
>>> better to ask on their lists :)
>>>
>>> -Val
>>>
>>>
>>>
>>> --
>>> View this message in context: http://apache-ignite-users.705
>>> 18.x6.nabble.com/Ignite-Cassandra-AWS-test-framework-tp9324p9347.html
>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>
>>>
>>>
>>
>

Re: Ignite Cassandra AWS test framework

2016-12-01 Thread Riccardo Iacomini

Hi Val,

No, that's not the issue. I would like to follow the AWS ignite-cassandra
framework guide on the documentation, but some files the documentation says
I should modify are not in the test-package after I build ignite from
source.

Just to be clear, this is the link to the guide I am actually trying to
follow:
https://apacheignite-mix.readme.io/docs/aws-infrastructure-deployment

Il 01 dic 2016 11:56 PM, "vkulichenko"  ha
scritto:

Hi Riccardo,

Do you mean that you have problems starting Cassandra? If so, I think it's
better to ask on their lists :)

-Val



--
View this message in context: http://apache-ignite-users.
70518.x6.nabble.com/Ignite-Cassandra-AWS-test-framework-tp9324p9347.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Ignite Cassandra AWS test framework

2016-12-01 Thread Riccardo Iacomini

I am trying to evaluate Cassandra and Ignite following the AWS deployment
guide in the documentation. I've built both Ignite 1.6 and 1.7 from source,
but in both cases the test package generated misses the configuration file
*bootstrap/aws/env.sh* I should modify according to the documentation. The
ganglia folder with the scripts for the deployment of the monitoring
cluster is missing too in *bootstrap/aws/. *How should I procede?

Thank you in advance for your time.

Riccardo Iacomini


*RDSLab*

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*
ignite-bootstrap.sh* script is the *1.6.*

Best Regards

Riccardo Iacomini


*RDSLab*

On Tue, Nov 29, 2016 at 11:18 PM, Igor Rudyak <irud...@gmail.com> wrote:

> Ok, thanks for the info.
>
> Igor
>
> On Tue, Nov 29, 2016 at 12:56 PM, Denis Magda <dma...@apache.org> 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.
>>
>> —
>> Denis
>>
>> On Nov 29, 2016, at 11:49 AM, Denis Magda <dma...@apache.org> wrote:
>>
>> 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 <irud...@gmail.com> wrote:
>>
>> 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 <dma...@apache.org> wrote:
>>
>>> 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 <
>>> riccardo.iacom...@rdslab.com> wrote:
>>>
>>> Hi Igor,
>>> I finally discovered what was causing the issue. The example provided
>>> <https://apacheignite.readme.io/docs/examples> in the Ignite
>>> documentation page has a subtle difference in the package structure of
>>> several classes, for example:
>>>
>>> org.apache.ignite.cache.store.cassandra.datasource.DataSource (the
>>> class in the ignite-cassandra.jar) vs org.apache.ignite.cache.sto
>>> re.cassandra.*utils*.datasource.DataSource (in the example). The same
>>> applies also for other classes in the example. I do not know if this is due
>>> to a refactoring performed on the code which did not propagates through the
>>> examples, or simply I used a different version of the documentation in
>>> contrast with the one I was running.
>>>
>>> Anyway, thank you for your time.
>>>
>>> Best regards
>>>
>>> Riccardo Iacomini
>>>
>>>
>>> *RDSLab*
>>>
>>> On Mon, Nov 28, 2016 at 5:34 PM, Igor Rudyak <irud...@gmail.com> wrote:
>>>
>>>> If you are using ignite.sh it should be fine.
>>>>
>>>> Igor
>>>>
>>>> On Nov 28, 2016 8:29 AM, "Riccardo Iacomini" <
>>>> riccardo.iacom...@rdslab.com> wrote:
>>>>
>>>>> I will try. Yes I am using the ignite.sh command. Any drawbacks?
>>>>>
>>>>> Il 28 nov 2016 5:26 PM, "Igor Rudyak" <irud...@gmail.com> ha scritto:
>>>>>
>>>>> 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" <
>>>>> riccardo.iacom...@rdslab.com> wrote:
>>>>>
>>>>>> 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 <https://apacheignite.readme.io/v1.5/docs/docker-deployment> in
>>>>>> the documentation. Do you have any other suggestion?
>>>>>>
>>>>>> Thanks for your patience.
>>>>>>
>>>>>> Best regards
>>>>>&g

Re: Cassandra basic setup

2016-11-29 Thread Riccardo Iacomini

Hi Igor,
I finally discovered what was causing the issue. The example provided
<https://apacheignite.readme.io/docs/examples> in the Ignite documentation
page has a subtle difference in the package structure of several classes,
for example:

org.apache.ignite.cache.store.cassandra.datasource.DataSource (the class in
the ignite-cassandra.jar) vs org.apache.ignite.cache.store.cassandra.*utils*
.datasource.DataSource (in the example). The same applies also for other
classes in the example. I do not know if this is due to a refactoring
performed on the code which did not propagates through the examples, or
simply I used a different version of the documentation in contrast with the
one I was running.

Anyway, thank you for your time.

Best regards

Riccardo Iacomini


*RDSLab*

On Mon, Nov 28, 2016 at 5:34 PM, Igor Rudyak <irud...@gmail.com> wrote:

> If you are using ignite.sh it should be fine.
>
> Igor
>
> On Nov 28, 2016 8:29 AM, "Riccardo Iacomini" <riccardo.iacom...@rdslab.com>
> wrote:
>
>> I will try. Yes I am using the ignite.sh command. Any drawbacks?
>>
>> Il 28 nov 2016 5:26 PM, "Igor Rudyak" <irud...@gmail.com> ha scritto:
>>
>> 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" <
>> riccardo.iacom...@rdslab.com> wrote:
>>
>>> 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
>>> <https://apacheignite.readme.io/v1.5/docs/docker-deployment> in the
>>> documentation. Do you have any other suggestion?
>>>
>>> Thanks for your patience.
>>>
>>> Best regards
>>>
>>> Riccardo Iacomini
>>>
>>>
>>> *RDSLab*
>>>
>>> On Sun, Nov 27, 2016 at 8:46 PM, Igor Rudyak <irud...@gmail.com> wrote:
>>>
>>>> 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 specifying username and password
>>>>> in the bean's properties. Anyway, I cannot get it work. Ignite still 
>>>>> cannot
>>>>> find the required classes, this time 
>>>>> *org.apache.ignite.cache.store.cassandra.utils.datasource.DataSource.
>>>>> *The class is indeed located in the jar ignite-cassandra-1.7.0.jar in
>>>>> IGNITE_HOME/modules/cassandra/target. I tried adding the path to
>>>>> USER_LIBS and CLASSPATH, no different behavior. Maybe the environment
>>>>> variables got ignored?
>>>>>
>>>>>
>>>>> Riccardo Iacomini
>>>>>
>>>>>
>>>>> *RDSLab*
>>>>>
>>>>> On Wed, Nov 23, 2016 at 7:41 PM, Igor Rudyak <irud...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> 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.
>>>>>>
>>>>>> Also if you want to use Cassandra as a persistent store you actually
>>>>>> don't need *CassandraAdminCredentials  *cause it's just used for
>>>>>> tests.
>>>>>>
>>>>>> Igor
>>>>>>
>>>>>> On Wed, Nov 23, 2016 at 7:33 AM, Riccardo Iacomini <
>>>>>> riccardo.iacom...@rdslab.com> wrote:
>>>>>>
>>>>>>> Following the example <https://apacheignite.readme.io/docs/examples>
>>>>>>> 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
>>>>>>> message:
>>>>>>>
>>>>>>> *class org.apache.ignite.IgniteException: Failed to instantiate
>>>>>>> Spring XML application context (make sure all classes used in Spring
>>>>>>> configuration are present at CLASSPATH*
>>>>>>>
>>>>>>> CassandraAdminCredentials is the class not being found. Commenting
>>>>>>> the bean, I get the same for the next class. I tried adding the path to 
>>>>>>> the
>>>>>>> jar *ignite-cassandra-1.7.0.jar *to both CLASSPATH and USER_LIBS,
>>>>>>> still not getting found. Opening the jar I cannot find the requested 
>>>>>>> class.
>>>>>>> Am I missing some dependencies?
>>>>>>>
>>>>>>> Thank you for your help.
>>>>>>>
>>>>>>> Riccardo Iacomini
>>>>>>>
>>>>>>>
>>>>>>> *RDSLab*
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>

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
<https://apacheignite.readme.io/v1.5/docs/docker-deployment> in the
documentation. Do you have any other suggestion?

Thanks for your patience.

Best regards

Riccardo Iacomini


*RDSLab*

On Sun, Nov 27, 2016 at 8:46 PM, Igor Rudyak <irud...@gmail.com> wrote:

> 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 specifying username and password
>> in the bean's properties. Anyway, I cannot get it work. Ignite still cannot
>> find the required classes, this time 
>> *org.apache.ignite.cache.store.cassandra.utils.datasource.DataSource.
>> *The class is indeed located in the jar ignite-cassandra-1.7.0.jar in
>> IGNITE_HOME/modules/cassandra/target. I tried adding the path to
>> USER_LIBS and CLASSPATH, no different behavior. Maybe the environment
>> variables got ignored?
>>
>>
>> Riccardo Iacomini
>>
>>
>> *RDSLab*
>>
>> On Wed, Nov 23, 2016 at 7:41 PM, Igor Rudyak <irud...@gmail.com> wrote:
>>
>>> 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.
>>>
>>> Also if you want to use Cassandra as a persistent store you actually
>>> don't need *CassandraAdminCredentials  *cause it's just used for tests.
>>>
>>> Igor
>>>
>>> On Wed, Nov 23, 2016 at 7:33 AM, Riccardo Iacomini <
>>> riccardo.iacom...@rdslab.com> wrote:
>>>
>>>> Following the example <https://apacheignite.readme.io/docs/examples>
>>>> 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
>>>> message:
>>>>
>>>> *class org.apache.ignite.IgniteException: Failed to instantiate Spring
>>>> XML application context (make sure all classes used in Spring configuration
>>>> are present at CLASSPATH*
>>>>
>>>> CassandraAdminCredentials is the class not being found. Commenting the
>>>> bean, I get the same for the next class. I tried adding the path to the 
>>>> jar *ignite-cassandra-1.7.0.jar
>>>> *to both CLASSPATH and USER_LIBS, still not getting found. Opening the
>>>> jar I cannot find the requested class. Am I missing some dependencies?
>>>>
>>>> Thank you for your help.
>>>>
>>>> Riccardo Iacomini
>>>>
>>>>
>>>> *RDSLab*
>>>>
>>>
>>>
>>
>

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
*org.apache.ignite.cache.store.cassandra.utils.datasource.DataSource.
*The class is indeed located in the jar ignite-cassandra-1.7.0.jar in
IGNITE_HOME/modules/cassandra/target. I tried adding the path to USER_LIBS
and CLASSPATH, no different behavior. Maybe the environment variables got
ignored?


Riccardo Iacomini


*RDSLab*

On Wed, Nov 23, 2016 at 7:41 PM, Igor Rudyak <irud...@gmail.com> wrote:

> 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.
>
> Also if you want to use Cassandra as a persistent store you actually don't
> need *CassandraAdminCredentials  *cause it's just used for tests.
>
> Igor
>
> On Wed, Nov 23, 2016 at 7:33 AM, Riccardo Iacomini <
> riccardo.iacom...@rdslab.com> wrote:
>
>> Following the example <https://apacheignite.readme.io/docs/examples>
>> 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
>> message:
>>
>> *class org.apache.ignite.IgniteException: Failed to instantiate Spring
>> XML application context (make sure all classes used in Spring configuration
>> are present at CLASSPATH*
>>
>> CassandraAdminCredentials is the class not being found. Commenting the
>> bean, I get the same for the next class. I tried adding the path to the jar 
>> *ignite-cassandra-1.7.0.jar
>> *to both CLASSPATH and USER_LIBS, still not getting found. Opening the
>> jar I cannot find the requested class. Am I missing some dependencies?
>>
>> Thank you for your help.
>>
>> Riccardo Iacomini
>>
>>
>> *RDSLab*
>>
>
>

Cassandra basic setup

2016-11-23 Thread Riccardo Iacomini

Following the example <https://apacheignite.readme.io/docs/examples>
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
message:

*class org.apache.ignite.IgniteException: Failed to instantiate Spring XML
application context (make sure all classes used in Spring configuration are
present at CLASSPATH*

CassandraAdminCredentials is the class not being found. Commenting the
bean, I get the same for the next class. I tried adding the path to
the jar *ignite-cassandra-1.7.0.jar
*to both CLASSPATH and USER_LIBS, still not getting found. Opening the jar
I cannot find the requested class. Am I missing some dependencies?

Thank you for your help.

Riccardo Iacomini


*RDSLab*

Ignite Info

Configuring SQL queries - ClassNotFoundException: Unknown pair

Re: ODBC driver issue

Re: ODBC driver issue

Re: ODBC driver issue

Re: ODBC driver issue

Re: ODBC driver issue

Cassandra cache info

Re: Ignite Cassandra AWS test framework

Re: Ignite Cassandra AWS test framework

Ignite Cassandra AWS test framework

Re: Cassandra basic setup

Re: Cassandra basic setup

Re: Cassandra basic setup

Re: Cassandra basic setup

Cassandra basic setup

16 matches

Site Navigation

Mail list logo

Footer information