Re: error in ignite-spark

[Mehdi Seydali]

i have searched alot  but i couldn't find enable scala profile i maven. do
you have any link?

On Wed, Dec 26, 2018 at 8:34 PM Ilya Kasnacheev 
wrote:

> Hello!
>
> With -Pscala command or via netbeans dialogs.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 26 дек. 2018 г. в 19:54, Mehdi Seydali :
>
>> How could i enable scala profile??
>>
>> On Wed, 26 Dec 2018, 13:44 Ilya Kasnacheev, 
>> wrote:
>>
>>> Hello!
>>>
>>> You have to enable 'scala' profile in Maven to be able to build Spark
>>> examples. However, even after I rebuild with scala profile, netbeans will
>>> not show them propetly. You will still be able to run them all right, I
>>> think.
>>>
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>>
>>>
>>> ср, 26 дек. 2018 г. в 12:27, mehdi sey :
>>>
 hi. i want to execute a RDD example in spark from example folder of
 ignite
 2.7, but i have encounter and error just like an attached picture. in
 import
 section you see an underlined line. i have added dependency but still is
 remained why?

 <
 http://apache-ignite-users.70518.x6.nabble.com/file/t2160/Screenshot_from_2018-12-26_10-31-16.png>

 <
 http://apache-ignite-users.70518.x6.nabble.com/file/t2160/Screenshot_from_2018-12-26_10-34-19.png>




 --
 Sent from: http://apache-ignite-users.70518.x6.nabble.com/

>>>

Re: Ouch! Argument is invalid: Cache name must not be null or empty.

[Evgenii Zhuravlev]

As you see, the example in config has , which means that it's
just a part of the configuration. Exceptions message says "Cache name must
not be null" and that really the problem that you faced, just define cache
name property to resolve this issue.

Evgenii


чт, 27 дек. 2018 г. в 22:28, yangjiajun <1371549...@qq.com>:

> Hello.
>
> I use ignite 2.6 as a database and try to tune data rebalancing according
> to
> following doc：
>
> https://apacheignite.readme.io/docs/rebalancing#section-rebalance-message-throttling
> But I get an exception when I set those settings.
>
> class org.apache.ignite.IgniteException: Ouch! Argument is invalid: Cache
> name must not be null or empty.
> at
>
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:990)
> at org.apache.ignite.Ignition.start(Ignition.java:355)
> at
>
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
> Caused by: class org.apache.ignite.IgniteCheckedException: Ouch! Argument
> is
> invalid: Cache name must not be null or empty.
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1133)
> at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014)
> at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723)
> at
> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151)
> at
>
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1069)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:955)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:854)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:724)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:693)
> at org.apache.ignite.Ignition.start(Ignition.java:352)
> ... 1 more
> Caused by: java.lang.IllegalArgumentException: Ouch! Argument is invalid:
> Cache name must not be null or empty.
> at
>
> org.apache.ignite.internal.util.GridArgumentCheck.ensure(GridArgumentCheck.java:109)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheUtils.validateCacheName(GridCacheUtils.java:1590)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoin(GridCacheProcessor.java:738)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoinFromConfig(GridCacheProcessor.java:808)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:707)
> at
>
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1739)
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:980)
> ... 10 more
> Failed to start grid: Ouch! Argument is invalid: Cache name must not be
> null
> or empty.
>
>
> Here is my config file:
> example-default2.xml
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t2059/example-default2.xml>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Ouch! Argument is invalid: Cache name must not be null or empty.

[yangjiajun]

Hello.

I use ignite 2.6 as a database and try to tune data rebalancing according to
following doc：
https://apacheignite.readme.io/docs/rebalancing#section-rebalance-message-throttling
But I get an exception when I set those settings.

class org.apache.ignite.IgniteException: Ouch! Argument is invalid: Cache
name must not be null or empty.
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:990)
at org.apache.ignite.Ignition.start(Ignition.java:355)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
Caused by: class org.apache.ignite.IgniteCheckedException: Ouch! Argument is
invalid: Cache name must not be null or empty.
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1133)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723)
at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1069)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:955)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:854)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:724)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:693)
at org.apache.ignite.Ignition.start(Ignition.java:352)
... 1 more
Caused by: java.lang.IllegalArgumentException: Ouch! Argument is invalid:
Cache name must not be null or empty.
at
org.apache.ignite.internal.util.GridArgumentCheck.ensure(GridArgumentCheck.java:109)
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.validateCacheName(GridCacheUtils.java:1590)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoin(GridCacheProcessor.java:738)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoinFromConfig(GridCacheProcessor.java:808)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:707)
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1739)
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:980)
... 10 more
Failed to start grid: Ouch! Argument is invalid: Cache name must not be null
or empty.


Here is my config file:
example-default2.xml

  



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Unsubscribe

[Ravi kumar Puri]

Unsubscribe

Re: error in importing ignite 2.7 to netbeans

[Mehdi Seydali]

pom content file in /example/src/ just like bellow. i think profile has set.




http://maven.apache.org/POM/4.0.0; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0


org.apache.ignite
ignite-parent
1
../parent


ignite-examples
2.7.0



javax.cache
cache-api
${javax.cache.version}



org.apache.ignite
ignite-core
${project.version}



org.apache.ignite
ignite-spring
${project.version}



org.springframework
spring-core


org.springframework
spring-beans





org.apache.ignite
ignite-log4j
${project.version}



org.apache.ignite
ignite-indexing
${project.version}



org.apache.ignite
ignite-spring-data_2.0
${project.version}



org.apache.ignite
ignite-ml
${project.version}



commons-cli
commons-cli
1.2



com.google.code.simple-spring-memcached
spymemcached
2.8.4



org.apache.ignite
ignite-core
${project.version}
test-jar
test



org.gridgain
ignite-shmem
1.0.0
test



org.javassist
javassist
${javassist.version}
test





src/main/java
src/test/java
src/main/java
src/test/java




scala


src/main/spark
src/test/spark




org.apache.ignite
ignite-scalar
${project.version}



org.scalatest
scalatest_2.11
2.2.4
test


org.scala-lang
scala-library





org.apache.ignite
ignite-spark
${project.version}






net.alchim31.maven
scala-maven-plugin






lgpl


src/main/java-lgpl
src/test/java-lgpl




org.apache.ignite
ignite-hibernate_5.1
${project.version}



org.apache.ignite
ignite-schedule
${project.version}



org.apache.ignite
ignite-geospatial
${project.version}








src/main/java

**/*.java



config





org.codehaus.mojo
build-helper-maven-plugin


add-sources
generate-sources

add-source



${lgpl.folder}
${spark.folder}





add-tests
generate-test-sources

add-test-source



${lgpl.test.folder}
${spark.test.folder}







org.apache.maven.plugins
maven-deploy-plugin

true

   

Re: error in importing ignite 2.7 to netbeans

[Mehdi Seydali]

In which file i can see the profile?pom in the root folder of ignite?


On Wednesday, December 26, 2018, aealexsandrov 
wrote:

> Please check that you set the scale profile because of without it the spark
> dependencies will not be added:
>
> ...
> 
> 
> scala
>
> 
> src/main/spark
> 
>
> 
> 
> org.apache.ignite
> ignite-scalar
> 2.7.0
> 
>
> 
> org.apache.ignite
> ignite-spark
> 2.7.0
> 
> 
> ...
>
> BR,
> Andrei
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Data Replication Between Ignite Clusters Through Kafka

[Prashant Murthy]

Hi,

Can anyone suggest me know how to achieve the data replication across
clusters for ignite? What needs to be corrected to make it work as mentioned
in previous post.

Thanks,
Prashant



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Remote Node

[Evgenii Zhuravlev]

Hi,

By default, Ignite uses TcpDiscoveryMulticastIpFinder, which means that
nodes can be connected to each other even without configuring certain IP
addresses. You can use TcpDiscoveryVmIpFinder instead, it will try to
connect only to the pre-configured addresses.

TcpDiscoverySpi discovery = new TcpDiscoverySpi().setIpFinder(new
TcpDiscoveryVmIpFinder().setAddresses(Collections.singleton("127.0.0.1:47500
..47509")));

Evgenii

чт, 27 дек. 2018 г. в 09:37, Skollur :

> Hello
>
> I have upgraded my code from Apache ignite version 2.6 to 2.7. I am running
> two server nodes in two different machines. However after upgrade, noticed
> that these two server nodes joined. Log shows as servers=2, state=ACTIVE.
>
> Based on previous suggestion, I have commented out TCPDiscoverSPI and still
> see server nodes are joined in 2.7 version. How to make sure server nodes
> runs in one machine and not joining with remote (stand alone)?
>
> IgniteConfiguration cfg = new IgniteConfiguration();
> cfg.setIgniteInstanceName("testdb");
>
> /*TcpDiscoverySpi discovery = new TcpDiscoverySpi();
>
>
> discovery.setLocalAddress(IPClusterConfigInitialize.IpClusterConfig().getProperty("ipClusterConfig"));
> discovery.setLocalPort(new
> Integer(IPClusterConfigInitialize.IpClusterConfig().getProperty("port")));
> cfg.setDiscoverySpi(discovery);*/
>
> cfg.setPeerClassLoadingEnabled(false);
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Ignite Remote Node

[Skollur]

Hello

I have upgraded my code from Apache ignite version 2.6 to 2.7. I am running
two server nodes in two different machines. However after upgrade, noticed
that these two server nodes joined. Log shows as servers=2, state=ACTIVE.

Based on previous suggestion, I have commented out TCPDiscoverSPI and still
see server nodes are joined in 2.7 version. How to make sure server nodes
runs in one machine and not joining with remote (stand alone)?

IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setIgniteInstanceName("testdb");

/*TcpDiscoverySpi discovery = new TcpDiscoverySpi();
   
discovery.setLocalAddress(IPClusterConfigInitialize.IpClusterConfig().getProperty("ipClusterConfig"));
discovery.setLocalPort(new
Integer(IPClusterConfigInitialize.IpClusterConfig().getProperty("port")));
cfg.setDiscoverySpi(discovery);*/

cfg.setPeerClassLoadingEnabled(false);





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Index inline size

[Denis Mekhanikov]

Prasad,

By default *QuerySqlField#inlineSize *is equal to -1, which means, that it
will be chosen automatically.
*CacheConfiguration#setSqlIndexMaxInlineSize *specifies the maximal
automatically calculated
inline size for a cache.
But if *QuerySqlField#inlineSize *is not -1, then it will be used
regardless of the configured maximum.
It should only be less than 2048. Otherwise 2048 will be used.

Judging by the warning message, value 10 is used for the inline size.
Did you specify it manually or was it calculated automatically?

Index inlining documentation:
https://apacheignite-sql.readme.io/docs/create-index#section-index-inlining

Denis

ср, 26 дек. 2018 г. в 18:27, Prasad Bhalerao :

> Hi,
>
> I have set sqlIndexMaxInline size in cache configuration level as follows.
>
> cacheCfg.setSqlIndexMaxInlineSize(100);
>
> But still  I am getting following warning message in log.
>
> WARN  o.a.i.i.p.q.h2.database.H2TreeIndex -  Indexed
> columns of a row cannot be fully inlined into index what may lead to
> slowdown due to additional data page reads, increase index inline size if
> needed (use INLINE_SIZE option for CREATE INDEX command,
> QuerySqlField.inlineSize for annotated classes, or QueryIndex.inlineSize
> for explicit QueryEntity configuration) [cacheName=USERACCOUNTDATA,
> tableName=USER_ACCOUNT_CACHE, idxName=USER_ACCOUNT_IDX4,
> idxCols=(SUBSCRIPTIONID, UNITID, _KEY, AFFINITYID), idxType=SECONDARY,
> curSize=10, recommendedInlineSize=83]
>
> 1) Is it necessary to set inline size using @QuerySqlField annotation?
>
> 2) How do I set inline size in case of group index in following case?
> Do I need to set inline property inside each @QuerySqlField annotation?
>
> public class Person implements Serializable {
>   /** Indexed in a group index with "salary". */
>   @QuerySqlField(orderedGroups={@QuerySqlField.Group(
> name = "age_salary_idx", order = 0, descending = true)})
>   private int age;
>
>   /** Indexed separately and in a group index with "age". */
>   @QuerySqlField(index = true, orderedGroups={@QuerySqlField.Group(
> name = "age_salary_idx", order = 3)})
>   private double salary;
> }
>
>
>
>
>
>
>
> Thanks,
> Prasad
>

Re: Failed to initialize wal (work directory contains incorrect number of segments) [cur=357, expected=10]

[aealexsandrov]

Thank you,

I will try to reproduce the same.

Andrei



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to initialize wal (work directory contains incorrect number of segments) [cur=357, expected=10]

[yangjiajun]

Hello.

I only started one node.

Here is my config file:

example-default.xml
 
 


aealexsandrov wrote
> No,
> 
> I just try to get the details and reproduce the issue. Possible there is
> an
> issue here. I will return with an update soon.
> 
> Also could you please provide the configuration of your nodes? Did you
> update the walArchivePath for all of your nodes?
> 
> BR,
> Andrei
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to initialize wal (work directory contains incorrect number of segments) [cur=357, expected=10]

[aealexsandrov]

No,

I just try to get the details and reproduce the issue. Possible there is an
issue here. I will return with an update soon.

Also could you please provide the configuration of your nodes? Did you
update the walArchivePath for all of your nodes?

BR,
Andrei



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to initialize wal (work directory contains incorrect number of segments) [cur=357, expected=10]

[yangjiajun]

Hello.Thanks for your reply.

I use version 2.6.

I changed the walArchivePath to the directory where before was walPath.

So the correct operation is to set the walPath to the directory where before
was walArchivePath?



aealexsandrov wrote
> Hi,
> 
> What is the version of Ignite you use?
> 
> Did you set the walPath to the directory where before was walArchivePath?
> 
> BR,
> Andei
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to initialize wal (work directory contains incorrect number of segments) [cur=357, expected=10]

[yangjiajun]

aealexsandrov wrote
> Hi,
> 
> What is the version of Ignite you use?
> 
> Did you set the walPath to the directory where before was walArchivePath?
> 
> BR,
> Andei
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to initialize wal (work directory contains incorrect number of segments) [cur=357, expected=10]

[aealexsandrov]

Hi,

What is the version of Ignite you use?

Did you set the walPath to the directory where before was walArchivePath?

BR,
Andei



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Failed to initialize wal (work directory contains incorrect number of segments) [cur=357, expected=10]

[yangjiajun]

Hello.

I want to disable wal archiving by setting  WAL path and the WAL archive
path to the same value.
https://apacheignite.readme.io/docs/write-ahead-log
I make this change and then success restart my node first time.But I get an
exception when I restart my node second time.Is my change a dangerous
operation？Can I recover it? 

Here is the exception:

[21:22:22,321][SEVERE][main][IgniteKernal] Exception during start
processors, node will be stopped and close connections
class org.apache.ignite.IgniteCheckedException: Failed to start processor:
GridProcessorAdapter []
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1742)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:980)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1069)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:955)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:854)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:724)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:693)
at org.apache.ignite.Ignition.start(Ignition.java:352)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
initialize wal (work directory contains incorrect number of segments)
[cur=357, expected=10]
at
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager.checkOrPrepareFiles(FsyncModeFileWriteAheadLogManager.java:1112)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager.start0(FsyncModeFileWriteAheadLogManager.java:348)
at
org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.start(GridCacheSharedManagerAdapter.java:61)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:700)
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1739)
... 11 more



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite we-console security

[Alexey Kuznetsov]

Hi, Sheshananda!

I merged IGNITE-9845 to master. And it will be available in Ignite 2.8.
This will allow to configure SSL for Web Console in "DEV" mode and in
"Direct install" mode.

Please, note that IGNITE-10668 is under development for now.
When finished, it will enable SSL configuration in "Docker" mode.

-- 
Alexey Kuznetsov

Re: If I want to know how long it takes for data reading from the server side, where should I add logs?

[aealexsandrov]

Hi,

Will be better if you shared your code. However, I see that you used
persistence. So here are some reasons why you can see these drops:

1)You data region is less than full loaded data size stored on disk. In case
if read operation can't find the value in RAM then it will read it from the
disk. In the case of RANDOM_2_LRU it means that this value will be stored in
RAM and some other value will be evicted from the memory.

So when you will try to read this value you could see some performance drop.

2)Another problem could be related to initial loading of the values to
memory from the disk. I think that before starting of the benchmark you
should to warm up the Ignite by reading of the stored values for some time.

Could you please check can these moments be applicable to you?

BR,
Andrei



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Is Apache planning to release support for table joins with updates .

[DS]

I am  looking solution  for queries  like below  :

Update Person SET  lastName ='pit' where person.id =city.id AND city.zipCode
='B8Q97'

OR

UPDATE table1, table2 SET table1.quantity = 6 where table1.pid =table2.pid
AND  table2.zip ="abc"





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: CAP Theorem (CP? or AP?)

[Stanislav Lukyanov]

There were two bugs actually, but the problem is basically the same, just in 
different cases.
SQL + Partition Loss Policies issue (fixed in 2.7) - 
https://issues.apache.org/jira/browse/IGNITE-8927 (the issue says “hang” but 
the visible behavior actually varies)
SQL + Partition Loss Policies + Native Persistence issue (fixed in 2.8) - 
https://issues.apache.org/jira/browse/IGNITE-9841

If you don’t use native persistence then various SELECTs should work as you 
expect on 2.7.
If you do need persistence then you could try working with master (e.g. take a 
nightly build – but don’t use it in any real environments).

Stan

From: joseheitor
Sent: 24 декабря 2018 г. 18:40
To: user@ignite.apache.org
Subject: Re: CAP Theorem (CP? or AP?)

Guys, thank you both for your informative and helpful responses.

I have explicitly configured the cache-template with the additional
property:



And have observed the following behaviour:

1. [OK] Attempting to get a specific record(s) which resides in a lost
partition does indeed return an exception, as expected.

2. [?] Doing a SELECT COUNT(*) however, still succeeds without error, but
obviously reports the wrong number of total records (understandably). But
shouldn't any operation against a cache with lost partitions result in an
Exception? How will my application know that the result is valid and can be
trusted to be accurate?

Another question please - Stanislav, what is the issue with Ignite
persistence, that was fixed in 2.7 for in-memory, but will only be fixed for
Ignite native persistence in version 2.8...?

Thanks,
Jose



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/