Re: NullPointerException in GridCacheTtlManager.expire

[Bellenger, Dominique]

Thank you for the information! What are the worst consequences if I hit that 
bug? Entries not being evicted?
Is my tx committed if the error is striking on commit or do I need to redo the 
work that was done in the tx?

On 12. Apr 2018, at 14:30, Andrey Mashenkov 
> wrote:

Hi Dome,

It is known issue and there is a ticket for this [1] you can track.

It is hard to be reproduced due to a race.
Seems, GridCacheUtils.unwindEvicts() should check if context has been started.


[1] https://issues.apache.org/jira/browse/IGNITE-7972


On Thu, Apr 12, 2018 at 2:39 PM, dkarachentsev 
> wrote:
Hi Dome,

Could you please attach full logs?

Thanks!
-Dmitry



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



--
Best regards,
Andrey V. Mashenkov

Re: Primary and Backups caches questions.

[vkulichenko]

Hi Mauricio,

1. This is correct.

2. Queries return the actual data, therefore you see every entry only once.
The fact that there are backups is internal and is not related to query
results. And actually, I don't think the check you're doing is valid because
different queries are not in sync with each other. If you need to make sure
that primary and backup is consistent at all times, you can use FULL_SYNC
mode:
https://apacheignite.readme.io/docs/primary-and-backup-copies#synchronous-and-asynchronous-backups

3. What is your goal here exactly? Do you only try to understand how it
works, or listening to backup copies is required by application logic? If
the former, I suggest you just put a breakpoint in debug and trace the
execution. If the latter, then it's a bit weird and you probably should
revisit the approach.

-Val



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

Re: SQL Transactional Support for Commit and rollback operation.

[Denis Magda]

Hi Rizal,

It will be served hot to your doors soon. Please stay tuned ;)

--
Denis

On Wed, Apr 11, 2018 at 6:21 PM, rizal123  wrote:

> Dear Ignite Masters,
>
> Yes, i also need this features. I hope it will be release soon. I hope.. :)
>
> I have to pending my project 'mirgate oracle to ignite', cause of this.
>
> Thanks,
> Rizal
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Primary and Backups caches questions.

[Mauricio]

Hi All. I have the following scenario. My cluster has 12 nodes. I have one
PARTITIONED cache named Documents and the type is  also the
number of backups of this cache is 1. 

My questions are the following:
1. Having my number of backups equals to 1, this means that any entry will
be stored in two different servers at any time. I believe one copy of the
entry must to be in the PRIMARY node of that partition and another second
copy should be in the BACKUP node for that partition. Does my assumption is
correct on this?

2. I was running a ScanQuery with local set to true in all of the nodes, it
means 12 times the same query, however only one node returns the entry that
I was looking for, which makes me think that the scan query is running only
over the PRIMARY cache in each of the nodes, I believe the scan query does
not consider the records that are stored in the BACKUP cache within the same
node, this is correct ?. If so it is possible to run a query that also
checks the BACKUP cache on the same node (check the PRIMARY and BACKUP on
each node). Having this will allow me to know if the record is the same in
the primary and within the backups or if they are not in sync when they
suppose to be.

My query was simple: 
ScanQuery scanQuery = new ScanQuery<>(
(IgniteBiPredicate) (uuid, doc) -> {
if (uuid.equals(UUID.fromString(originalUUID))) {
return true;
}
return false;
});
scanQuery.setLocal(true);

The result was empty in all of the nodes except in one of them, but I expect
that at least in two of them the response wasn't null, as I have one BACKUP
for each cache.

3. One last thing I was trying to verify how the propagation of the records
from the PRIMARY to the BACKUPS happens, I tried enabling events on the
cluster but that seems to be crazy expensive and bring my cluster to its
knees what I did was use (EVT_CACHE_OBJECT_PUT). 

Also I tried adding the cache listeners to the cache, but I get notice that
every single node hears that and the amount of logs is not ideal for my
purpose, I want to ask if there is a simple way like enable logging on a
specific class in which I can see some logging about when the cluster try to
save entries in the backups nodes for a specific cache and key? Also if
somebody can point me to some of the classes that are in charge of this
actions will be helpful.

Also, I tried the continuous query but again that does not seems to work as
I enable that in all of the host and the number of logs was not ideal,  I
just want to hear when a BACKUP cache receive a record to store on it. I
would like something like `HOST: received key= for cache=` but
just for attempts to write to the BACKUP caches.


Thanks in advance.





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

Re: NullPointerException in GridCacheTtlManager.expire

[Andrey Mashenkov]

Hi Dome,

It is known issue and there is a ticket for this [1] you can track.

It is hard to be reproduced due to a race.
Seems, GridCacheUtils.unwindEvicts() should check if context has been
started.


[1] https://issues.apache.org/jira/browse/IGNITE-7972


On Thu, Apr 12, 2018 at 2:39 PM, dkarachentsev 
wrote:

> Hi Dome,
>
> Could you please attach full logs?
>
> Thanks!
> -Dmitry
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>



-- 
Best regards,
Andrey V. Mashenkov

Re: FsyncModeFileWriteAheadLogManager cannot be cast to FileWriteAheadLogManager ERROR

[Ilya Lantukh]

Hi,

This is a bug that has already been fixed in
https://issues.apache.org/jira/browse/IGNITE-7865.

As a workaround, you can change WALMode value from FSYNC to any other mode,
or start Ignite with JVM property
-DIGNITE_WAL_FSYNC_WITH_DEDICATED_WORKER=true.

On Thu, Apr 12, 2018 at 2:18 PM, NO <727418...@qq.com> wrote:

> Hi
>
> AM using 2.4
>
> When I stop a node, other nodes will have an error log as follows
> =LOG==
> [2018-04-12T19:03:39,767][ERROR][sys-#317][GridCacheIoManager] Failed
> processing message [senderId=b541279a-78fb-4ab0-a9b2-a50f8f36823d, 
> msg=GridDhtPartitionsFullMessage
> [parts={-2100569601=GridDhtPartitionFullMap 
> [nodeId=b541279a-78fb-4ab0-a9b2-a50f8f36823d,
> nodeOrder=1, updateSeq=26, size=7], 1813334792=GridDhtPartitionFullMap
> [nodeId=b541279a-78fb-4ab0-a9b2-a50f8f36823d, nodeOrder=1, updateSeq=27,
> size=7]}, partCntrs=o.a.i.i.processors.cache.distributed.dht.preloader.
> IgniteDhtPartitionCountersMap@1804adec, partCntrs2=o.a.i.i.processors.
> cache.distributed.dht.preloader.IgniteDhtPartitionCountersMap2@13e9b15e,
> partHistSuppliers=o.a.i.i.processors.cache.distributed.dht.preloader.
> IgniteDhtPartitionHistorySuppliersMap@7e26cb82, partsToReload=o.a.i.i.
> processors.cache.distributed.dht.preloader.IgniteDhtPartitionsToReloadMap@275b7c67,
> topVer=AffinityTopologyVersion [topVer=10, minorTopVer=0], errs={},
> compress=false, resTopVer=AffinityTopologyVersion [topVer=10,
> minorTopVer=0], partCnt=2, super=GridDhtPartitionsAbstractMessage 
> [exchId=GridDhtPartitionExchangeId
> [topVer=AffinityTopologyVersion [topVer=10, minorTopVer=0],
> discoEvt=null, nodeId=2e0ca1a6, evt=NODE_LEFT], lastVer=GridCacheVersion
> [topVer=135010956, order=1523530985052, nodeOrder=8],
> super=GridCacheMessage [msgId=26154, depInfo=null, err=null,
> skipPrepare=false
> java.lang.ClassCastException: org.apache.ignite.internal.
> processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager cannot
> be cast to org.apache.ignite.internal.processors.cache.persistence.
> wal.FileWriteAheadLogManager
> at org.apache.ignite.internal.processors.cache.distributed.
> dht.preloader.GridDhtPartitionsExchangeFuture.logExchange(
> GridDhtPartitionsExchangeFuture.java:1639) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.distributed.
> dht.preloader.GridDhtPartitionsExchangeFuture.onDone(
> GridDhtPartitionsExchangeFuture.java:1620) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.distributed.
> dht.preloader.GridDhtPartitionsExchangeFuture.processFullMessage(
> GridDhtPartitionsExchangeFuture.java:2953) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.distributed.
> dht.preloader.GridDhtPartitionsExchangeFuture.access$1400(
> GridDhtPartitionsExchangeFuture.java:124) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.distributed.
> dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(
> GridDhtPartitionsExchangeFuture.java:2684) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.distributed.
> dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(
> GridDhtPartitionsExchangeFuture.java:2672) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.util.future.GridFutureAdapter.
> notifyListener(GridFutureAdapter.java:383) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.util.future.GridFutureAdapter.
> listen(GridFutureAdapter.java:353) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.distributed.
> dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveFullMessage(
> GridDhtPartitionsExchangeFuture.java:2672) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.
> GridCachePartitionExchangeManager.processFullPartitionUpdate(
> GridCachePartitionExchangeManager.java:1481)
> ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.
> GridCachePartitionExchangeManager.access$1100(
> GridCachePartitionExchangeManager.java:133) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.
> GridCachePartitionExchangeManager$3.onMessage(
> GridCachePartitionExchangeManager.java:339) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.
> GridCachePartitionExchangeManager$3.onMessage(
> GridCachePartitionExchangeManager.java:337) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.
> GridCachePartitionExchangeManager$MessageHandler.apply(
> GridCachePartitionExchangeManager.java:2689)
> ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.
> GridCachePartitionExchangeManager$MessageHandler.apply(
> GridCachePartitionExchangeManager.java:2668)
> ~[ignite-core-2.4.0.jar:2.4.0]
> at 

Re: NullPointerException in GridCacheTtlManager.expire

[dkarachentsev]

Hi Dome,

Could you please attach full logs?

Thanks!
-Dmitry



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

Re: FsyncModeFileWriteAheadLogManager cannot be cast to FileWriteAheadLogManager ERROR

[Ilya Kasnacheev]

Hello!

It looks like this problem fix have been scheduled for 2.5:
https://issues.apache.org/jira/browse/IGNITE-7865

I would recommend using walMode of LOG_ONLY for now, or adding a system
property -DIGNITE_WAL_FSYNC_WITH_DEDICATED_WORKER=true.

Your mileage may vary, but to me, LOG_ONLY looks safer than FSYNC with
occassionally failing exchange.

Regards,

-- 
Ilya Kasnacheev

2018-04-12 14:18 GMT+03:00 NO <727418...@qq.com>:

> Hi
>
> AM using 2.4
>
> When I stop a node, other nodes will have an error log as follows
> =LOG==
> [2018-04-12T19:03:39,767][ERROR][sys-#317][GridCacheIoManager] Failed
> processing message [senderId=b541279a-78fb-4ab0-a9b2-a50f8f36823d, 
> msg=GridDhtPartitionsFullMessage
> [parts={-2100569601=GridDhtPartitionFullMap 
> [nodeId=b541279a-78fb-4ab0-a9b2-a50f8f36823d,
> nodeOrder=1, updateSeq=26, size=7], 1813334792=GridDhtPartitionFullMap
> [nodeId=b541279a-78fb-4ab0-a9b2-a50f8f36823d, nodeOrder=1, updateSeq=27,
> size=7]}, partCntrs=o.a.i.i.processors.cache.distributed.dht.preloader.
> IgniteDhtPartitionCountersMap@1804adec, partCntrs2=o.a.i.i.processors.
> cache.distributed.dht.preloader.IgniteDhtPartitionCountersMap2@13e9b15e,
> partHistSuppliers=o.a.i.i.processors.cache.distributed.dht.preloader.
> IgniteDhtPartitionHistorySuppliersMap@7e26cb82, partsToReload=o.a.i.i.
> processors.cache.distributed.dht.preloader.IgniteDhtPartitionsToReloadMap@275b7c67,
> topVer=AffinityTopologyVersion [topVer=10, minorTopVer=0], errs={},
> compress=false, resTopVer=AffinityTopologyVersion [topVer=10,
> minorTopVer=0], partCnt=2, super=GridDhtPartitionsAbstractMessage 
> [exchId=GridDhtPartitionExchangeId
> [topVer=AffinityTopologyVersion [topVer=10, minorTopVer=0],
> discoEvt=null, nodeId=2e0ca1a6, evt=NODE_LEFT], lastVer=GridCacheVersion
> [topVer=135010956, order=1523530985052, nodeOrder=8],
> super=GridCacheMessage [msgId=26154, depInfo=null, err=null,
> skipPrepare=false
> java.lang.ClassCastException: org.apache.ignite.internal.
> processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager cannot
> be cast to org.apache.ignite.internal.processors.cache.persistence.
> wal.FileWriteAheadLogManager
> at org.apache.ignite.internal.processors.cache.distributed.
> dht.preloader.GridDhtPartitionsExchangeFuture.logExchange(
> GridDhtPartitionsExchangeFuture.java:1639) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.distributed.
> dht.preloader.GridDhtPartitionsExchangeFuture.onDone(
> GridDhtPartitionsExchangeFuture.java:1620) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.distributed.
> dht.preloader.GridDhtPartitionsExchangeFuture.processFullMessage(
> GridDhtPartitionsExchangeFuture.java:2953) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.distributed.
> dht.preloader.GridDhtPartitionsExchangeFuture.access$1400(
> GridDhtPartitionsExchangeFuture.java:124) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.distributed.
> dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(
> GridDhtPartitionsExchangeFuture.java:2684) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.distributed.
> dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(
> GridDhtPartitionsExchangeFuture.java:2672) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.util.future.GridFutureAdapter.
> notifyListener(GridFutureAdapter.java:383) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.util.future.GridFutureAdapter.
> listen(GridFutureAdapter.java:353) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.distributed.
> dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveFullMessage(
> GridDhtPartitionsExchangeFuture.java:2672) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.
> GridCachePartitionExchangeManager.processFullPartitionUpdate(
> GridCachePartitionExchangeManager.java:1481)
> ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.
> GridCachePartitionExchangeManager.access$1100(
> GridCachePartitionExchangeManager.java:133) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.
> GridCachePartitionExchangeManager$3.onMessage(
> GridCachePartitionExchangeManager.java:339) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.
> GridCachePartitionExchangeManager$3.onMessage(
> GridCachePartitionExchangeManager.java:337) ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.
> GridCachePartitionExchangeManager$MessageHandler.apply(
> GridCachePartitionExchangeManager.java:2689)
> ~[ignite-core-2.4.0.jar:2.4.0]
> at org.apache.ignite.internal.processors.cache.
> GridCachePartitionExchangeManager$MessageHandler.apply(
> 

FsyncModeFileWriteAheadLogManager cannot be cast to FileWriteAheadLogManager ERROR

[NO]

Hi

AM using 2.4

When I stop a node, other nodes will have an error log as follows
=LOG==
[2018-04-12T19:03:39,767][ERROR][sys-#317][GridCacheIoManager] Failed 
processing message [senderId=b541279a-78fb-4ab0-a9b2-a50f8f36823d, 
msg=GridDhtPartitionsFullMessage [parts={-2100569601=GridDhtPartitionFullMap 
[nodeId=b541279a-78fb-4ab0-a9b2-a50f8f36823d, nodeOrder=1, updateSeq=26, 
size=7], 1813334792=GridDhtPartitionFullMap 
[nodeId=b541279a-78fb-4ab0-a9b2-a50f8f36823d, nodeOrder=1, updateSeq=27, 
size=7]}, 
partCntrs=o.a.i.i.processors.cache.distributed.dht.preloader.IgniteDhtPartitionCountersMap@1804adec,
 
partCntrs2=o.a.i.i.processors.cache.distributed.dht.preloader.IgniteDhtPartitionCountersMap2@13e9b15e,
 
partHistSuppliers=o.a.i.i.processors.cache.distributed.dht.preloader.IgniteDhtPartitionHistorySuppliersMap@7e26cb82,
 
partsToReload=o.a.i.i.processors.cache.distributed.dht.preloader.IgniteDhtPartitionsToReloadMap@275b7c67,
 topVer=AffinityTopologyVersion [topVer=10, minorTopVer=0], errs={}, 
compress=false, resTopVer=AffinityTopologyVersion [topVer=10, minorTopVer=0], 
partCnt=2, super=GridDhtPartitionsAbstractMessage 
[exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=10, 
minorTopVer=0], discoEvt=null, nodeId=2e0ca1a6, evt=NODE_LEFT], 
lastVer=GridCacheVersion [topVer=135010956, order=1523530985052, nodeOrder=8], 
super=GridCacheMessage [msgId=26154, depInfo=null, err=null, 
skipPrepare=false
java.lang.ClassCastException: 
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager
 cannot be cast to 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.logExchange(GridDhtPartitionsExchangeFuture.java:1639)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1620)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processFullMessage(GridDhtPartitionsExchangeFuture.java:2953)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$1400(GridDhtPartitionsExchangeFuture.java:124)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(GridDhtPartitionsExchangeFuture.java:2684)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(GridDhtPartitionsExchangeFuture.java:2672)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:353)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveFullMessage(GridDhtPartitionsExchangeFuture.java:2672)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processFullPartitionUpdate(GridCachePartitionExchangeManager.java:1481)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1100(GridCachePartitionExchangeManager.java:133)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$3.onMessage(GridCachePartitionExchangeManager.java:339)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$3.onMessage(GridCachePartitionExchangeManager.java:337)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:2689)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:2668)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
 [ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
 [ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
 [ignite-core-2.4.0.jar:2.4.0]
at 

Re: Delete SQL is failing with IN clause for a table which has composite key

[Vladimir Ozerov]

Hi,

The problem is already fixed [1]. Fix will be available in AI 2.5.

[1] https://issues.apache.org/jira/browse/IGNITE-8147

On Wed, Apr 11, 2018 at 9:21 AM, Naveen  wrote:

> Hi
>
> These are the queries I have used, which I was getting the error every time
> I execute.
> Nothing else to share
>
> Thanks
> Naveen
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>