Hi!
That part of the code [1] starts Ignite client's node. In order to client's
node is working, sever node is required (instance of Ignite with
clientMode(false)). Do you run both those node in the same process or you
run separate spring boot instance?
Please note that in order to start server
Do your server node is also under spring boot or it is plain ignite assembly?
I did the following:
1. Start server node from regular ignite assembly
2. Run client with your configuration (build.gradle, mpm-ignite.xml)
All worked correct with changes described in my previous message.
Of course, I
Hi!
I reproduced exception with your configs.
I explored project dependencies and found newer version of H2 library.
The next string in build.gradle fixed exception for me:
compile group: 'com.h2database', name: 'h2', version: '1.4.191'
I'm not an expert in gradle and maybe there is more
Hi chevy!
I suppose that the issue in your configuration. Could you please provide
your pom.xml and mpm-ignite.xml?
Thanks,
Sergej
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8651.html
Sent from
Hi!
I have reproduced your issue with feature:istall ignite-core. I have also
same issue with ignite-indexing: lucene and h2 dependencies have not been
installed. The features.xml looks correct. Probably this is karaf issue.
As a workaround you can use jars from ignite release bundle [1].
About
Hi,
Discussion has been moved to another thread.
http://apache-ignite-users.70518.x6.nabble.com/KARAF-4-6-4-8-Snapshot-IgniteAbstractOsgiContextActivator-tc8552.html
--
View this message in context:
Hi!
As I know, "Resolved" is right state for fragment bundle.
You should not change MANIFEST files in ignite-* libraries. You should build
correct MANIFEST.MF in your own bundle.
Thanks,
Sergej
--
View this message in context:
Yes, sure.The query will be split into multiple map queries and a single
reduce query. Then all the map queries are executed on all data nodes,
providing results to the reducing node, which will in turn run the reduce
query over these intermediate results.
For more information check [1]
[1]
Hi, Anil!
What do you mean by "composite affinity key"? What problem you want to
solve?
If you want to use several fields as an affinity key, then you need to
create special class and use that class in entity key class.
For example:
class DepartmentAffinityKey {
private long companyId;
As I know JdkMarshaller used for serialization of internal ignite objects,
such as continuous query, distributed services etc., not for cache entries.
In your case the exception occured during deserialization of object
javax.cache.configuration.MutableConfiguration.
This class is from cache-api
Hi,
For internal activities ignite use only work directory.
Let me know if the issue is reproduced again.
-Sergej
--
View this message in context:
Hi M Singh!
I can't reproduce this. Could you provide your eclipse project?
-Sergej
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Iginte-Exception-Failed-to-unmarshal-discovery-data-for-component-1-on-starting-server-from-console-E-tp8160p8173.html
Sent from
Hi!
It looks like in thread [1].
Server and client spring contexts should have dataSource configuration.
Let me now if the solution from the tread won't help.
[1]
http://apache-ignite-users.70518.x6.nabble.com/Data-grid-client-errors-out-when-datasource-not-defined-tp7820p7854.html
-Sergej
Hi,
There is a ticket on this issue:
https://issues.apache.org/jira/browse/IGNITE-4043
Could you please look for that ticket.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cache-entry-list-on-particular-node-in-apache-ignite-tp8110p8113.html
Sent from the
14 matches
Mail list logo
