Re: Automated cache generation to clone a SQL schema?

2018-10-24 Thread sv
Does anyone have any idea about this?  



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


Off heap limit

2018-10-24 Thread Prasad Bhalerao
Hi,

Is there any limit for off heap memory?

Thanks,
Prasad


An error occured when recreate cache

2018-10-24 Thread Justin Ji
The following is the stack:

2018-10-25 03:47:02:992 [exchange-worker-#42] ERROR
o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture:498 - Failed to
reinitialize local partitions (preloading will be stopped):
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=1,
minorTopVer=1], discoEvt=DiscoveryCustomEvent
[customMsg=ChangeGlobalStateMessage
[id=5491559a661-f481a0dd-41dd-400f-9f16-78f1770bd576,
reqId=c18dfcb8-3874-48df-b88a-280270f3b2db,
initiatingNodeId=688cb8a6-b5b0-45e6-86d3-ad80d8dff395, activate=true,
baselineTopology=BaselineTopology [id=0, branchingHash=2124742757,
branchingType='New BaselineTopology',
baselineNodes=[2e713072-c9fd-4240-8e39-90751710e222]],
forceChangeBaselineTopology=false, timestamp=1540439222186],
affTopVer=AffinityTopologyVersion [topVer=1, minorTopVer=1],
super=DiscoveryEvent [evtNode=ZookeeperClusterNode
[id=688cb8a6-b5b0-45e6-86d3-ad80d8dff395, addrs=[172.17.42.1, 10.0.200.5,
127.0.0.1], order=1, loc=true, client=false], topVer=1, nodeId8=688cb8a6,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=154043997]],
nodeId=688cb8a6, evt=DISCOVERY_CUSTOM_EVT]
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:657) ~[?:1.8.0_171]
at java.util.ArrayList.get(ArrayList.java:433) ~[?:1.8.0_171]
at
org.apache.ignite.internal.processors.cache.CacheGroupContext.singleCacheContext(CacheGroupContext.java:385)
~[ignite-core-2.6.0.jar:2.6.0]
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.(GridDhtLocalPartition.java:198)
~[ignite-core-2.6.0.jar:2.6.0]
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.getOrCreatePartition(GridDhtPartitionTopologyImpl.java:812)
~[ignite-core-2.6.0.jar:2.6.0]
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.initPartitions(GridDhtPartitionTopologyImpl.java:368)
~[ignite-core-2.6.0.jar:2.6.0]
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.beforeExchange(GridDhtPartitionTopologyImpl.java:543)
~[ignite-core-2.6.0.jar:2.6.0]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1141)
~[ignite-core-2.6.0.jar:2.6.0]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:712)
[ignite-core-2.6.0.jar:2.6.0]
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2419)
[ignite-core-2.6.0.jar:2.6.0]
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2299)
[ignite-core-2.6.0.jar:2.6.0]
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
[ignite-core-2.6.0.jar:2.6.0]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
2018-10-25 03:47:02:993 [exchange-worker-#42] INFO 
o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture:478 - Finish exchange
future [startVer=AffinityTopologyVersion [topVer=1, minorTopVer=1],
resVer=null, err=java.lang.IndexOutOfBoundsException: Index: 0, Size: 0]
2018-10-25 03:47:02:996 [exchange-worker-#42] ERROR
o.a.i.i.p.c.GridCachePartitionExchangeManager:498 - Failed to wait for
completion of partition map exchange (preloading will not start):
GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryCustomEvent
[customMsg=null, affTopVer=AffinityTopologyVersion [topVer=1,
minorTopVer=1], super=DiscoveryEvent [evtNode=ZookeeperClusterNode
[id=688cb8a6-b5b0-45e6-86d3-ad80d8dff395, addrs=[172.17.42.1, 10.0.200.5,
127.0.0.1], order=1, loc=true, client=false], topVer=1, nodeId8=688cb8a6,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=154043997]],
crd=ZookeeperClusterNode [id=688cb8a6-b5b0-45e6-86d3-ad80d8dff395,
addrs=[172.17.42.1, 10.0.200.5, 127.0.0.1], order=1, loc=true,
client=false], exchId=GridDhtPartitionExchangeId
[topVer=AffinityTopologyVersion [topVer=1, minorTopVer=1],
discoEvt=DiscoveryCustomEvent [customMsg=null,
affTopVer=AffinityTopologyVersion [topVer=1, minorTopVer=1],
super=DiscoveryEvent [evtNode=ZookeeperClusterNode
[id=688cb8a6-b5b0-45e6-86d3-ad80d8dff395, addrs=[172.17.42.1, 10.0.200.5,
127.0.0.1], order=1, loc=true, client=false], topVer=1, nodeId8=688cb8a6,
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=154043997]],
nodeId=688cb8a6, evt=DISCOVERY_CUSTOM_EVT], added=true,
initFut=GridFutureAdapter [ignoreInterrupts=false, state=DONE, res=false,
hash=1419222410], init=false, lastVer=null,
partReleaseFut=PartitionReleaseFuture [topVer=AffinityTopologyVersion
[topVer=1, minorTopVer=1], futures=[ExplicitLockReleaseFuture
[topVer=AffinityTopologyVersion [topVer=1, minorTopVer=1], futures=[]],
AtomicUpdateReleaseFuture 

Re: npe: Failed to reinitialize local partition

2018-10-24 Thread wangsan
IgniteTwoRegionsRebuildIndexTest.java

  


The file is the test case.
I use getOrCreateCache with name. But the cache template I have beed defined
before.When reconnect ,It looks like the cache template not work.



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


Re: Cluster freeze with SSL enabled and JDK 11

2018-10-24 Thread Loredana Radulescu Ivanoff
Hello again,

I am working on getting the full SSL logs over to you, but I have one more
question in between: TLS v1.3 is enabled by default in JDK 11, and my app
is using TLS v1.2 specifically. There's a known issue that's recently
addressed by the JDK related to TLS v1.3 half close policy, details here:
https://bugs.java.com/view_bug.do?bug_id=8207009

Would you be able to confirm whether your SSL test runs successfully when
the connecting client/server use TLS v.12 specifically ?

FYI, I have tried specifically disabling TLS v1.3 using both the
"jdk.tls.client.protocols" and "jdk.tls.server.protocols" system
properties, and also set "jdk.tls.acknowledgeCloseNotify" to true on both
sides as indicated here - https://bugs.java.com/view_bug.do?bug_id=8208526

Based on my explorations so far, I think this may be a JDK issue
(specifically in the JSSE provider) that has not been addressed yet. Either
way, do you think three is anything that could be done in Ignite to
explicitly close the connection on both sides in a scenario like this ?

What I can safely share on the SSL logs so far is this (both nodes get
stuck, node 1 in failing to close the SSL connection, node 2 in waiting for
partition exchange)

Node 1:

"2018-10-23 14:18:40.981 PDT|SSLEngineImpl.java:715|Closing inbound of
SSLEngine
javax.net.ssl|ERROR|3F|grid-nio-worker-tcp-comm-1-#26%%|2018-10-23
14:18:40.981 PDT|TransportContext.java:313|Fatal (INTERNAL_ERROR): closing
inbound before receiving peer's close_notify (
"throwable" : {
  javax.net.ssl.SSLException: closing inbound before receiving peer's
close_notify
  at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:129)
  at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117)
  at
java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:308)
  at
java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:264)
  at
java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:255)
  at
java.base/sun.security.ssl.SSLEngineImpl.closeInbound(SSLEngineImpl.java:724)
  at
org.apache.ignite.internal.util.nio.ssl.GridNioSslHandler.shutdown(GridNioSslHandler.java:185)
  at
org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter.onSessionClosed(GridNioSslFilter.java:223)
  at
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedSessionClosed(GridNioFilterAdapter.java:95)
  at
org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onSessionClosed(GridNioServer.java:3447)
  at
org.apache.ignite.internal.util.nio.GridNioFilterChain.onSessionClosed(GridNioFilterChain.java:149)
  at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.close(GridNioServer.java:2689)
  at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2002)
  at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1764)
  at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
  at java.base/java.lang.Thread.run(Thread.java:834)}

)
2018-10-23 14:18:40.981 PDT|SSLSessionImpl.java:753|Invalidated session:
Session(1540329505125|TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)
DEBUG 14:18:40,981-0700 [] communication.tcp.TcpCommunicationSpi: Unable to
correctly close inbound data stream (will ignore) "


Server 2

"javax.net.ssl|DEBUG|46|tcp-disco-sock-reader-#4%%|2018-10-23 14:18:09.194
PDT|SSLSocketOutputRecord.java:310|WRITE: TLS12 application_data, length = 1
javax.net.ssl|DEBUG|46|tcp-disco-sock-reader-#4%%|2018-10-23 14:18:09.194
PDT|SSLCipher.java:1727|Plaintext before ENCRYPTION (
  : 01 .
)
javax.net.ssl|DEBUG|46|tcp-disco-sock-reader-#4%%|2018-10-23 14:18:09.194
PDT|SSLSocketOutputRecord.java:324|Raw write (
  : 17 03 03 00 19 00 00 00   00 00 00 00 A1 45 E5 C8  .E..
  0010: 27 3D EE E2 89 4A 0F DD   B6 9A 2A A8 5F 6B'=...J*._k
)
WARN 14:18:10,585-0700 [*Initialization*]
processors.cache.GridCachePartitionExchangeManager: Still waiting for
initial partition map exchange "

On Mon, Oct 22, 2018 at 12:31 AM Ilya Kasnacheev 
wrote:

> Hello!
>
> I would suggest regular (or DEBUG) Ignite logs + SSL debug logs.
>
>
> https://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/ReadDebug.html
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 19 окт. 2018 г. в 20:58, Loredana Radulescu Ivanoff <
> lradu...@tibco.com>:
>
>> Definitely - do you want debug logs, and if yes, should I enable them on
>> all Ignite packages, or just for certain ones? Any other diagnostic flags
>> that I should set?
>>
>> On Fri, Oct 19, 2018 at 7:48 AM Ilya Kasnacheev <
>> ilya.kasnach...@gmail.com> wrote:
>>
>>> Hello!
>>>
>>> Apache Ignite does not claim support JDK 11 at this moment. However, I
>>> was able to run SSL test (TcpDiscoverySslTrustedUntrustedTest) and it
>>> turned out mostly fine.
>>>
>>> More info is needed from your side, such as full instances logs.

Client node get stuck when reconnecting to cluster

2018-10-24 Thread Oleksandr Shevchenko

Hi all,

I have trouble to reconnect client node to cluster. Scenario I am running is

  1.  Ignite version 2.5 and Java 1.8
  2.  Two servers nodes running same machine with default GC set up
  3.  Client node runs on the same machine that servers do
  4.  Client node connects to cluster creates  cache name=TEST_CACHE  then 
destroy it  and then successfully completes then close client by calling 
ignite.close();
See client node log starting from line - [08:20:22,277][INFO][Test 
worker][GridDiscoveryManager] Topology snapshot [ver=5, servers=2, clients=1, 
CPUs=2, offheap=8.0GB, heap=1.8GB]
  5.  Client connects to cluster again to execute next sample operation but 
stucks starting from
[08:20:35,074][WARNING][exchange-worker-#212][diagnostic] Failed to wait for 
partition map exchange [topVer=AffinityTopologyVersion [topVer=7, 
minorTopVer=0], node=bd8d192b-bea3-4660-88c1-9949488f3249]. Consider changing 
TransactionConfiguration.txTimeoutOnPartitionMapSynchronization to non default 
value to avoid this message. Dumping pending objects that might be the cause:
  6.  Wait time for client to finally connect to cluster can be different(from 
10 secs up  10 mins) and  for sure depends on GC settings.  Also if connect to 
client JVM when it keeps complete partition exchange with jconsole and 
explicitly trigger System.gc this fix the problem.

Please advise possible solutions to fix subsequent client connect issues 
problem. Please let me know if more details needed to about the issue

Thanks in advance,
Oleksandr Shevchenko



ignite-client-conf.xml
Description: ignite-client-conf.xml


ignite-server-conf.xml
Description: ignite-server-conf.xml
>>>__    
>>>   /  _/ ___/ |/ /  _/_  __/ __/  
>>>  _/ // (7 7// /  / / / _/
>>> /___/\___/_/|_/___/ /_/ /___/   
>>> 
>>> ver. 2.5.0#20180523-sha1:86e110c7
>>> 2018 Copyright(C) Apache Software Foundation
>>> 
>>> Ignite documentation: http://ignite.apache.org

[08:20:17,129][INFO][Test worker][IgniteKernal] Config URL: 
file:/C:/Users/X217195/IdeaProjects/calculation-library/ignite-impl/build/resources/integrationTest/ignite-client-conf.xml
[08:20:17,140][INFO][Test worker][IgniteKernal] IgniteConfiguration 
[igniteInstanceName=null, pubPoolSize=8, svcPoolSize=8, callbackPoolSize=8, 
stripedPoolSize=8, sysPoolSize=8, mgmtPoolSize=4, igfsPoolSize=2, 
dataStreamerPoolSize=8, utilityCachePoolSize=8, 
utilityCacheKeepAliveTime=6, p2pPoolSize=2, qryPoolSize=8, 
igniteHome=H:\apache-ignite-fabric-2.4.0-bin, 
igniteWorkDir=H:\apache-ignite-fabric-2.4.0-bin\work, 
mbeanSrv=com.sun.jmx.mbeanserver.JmxMBeanServer@763335f9, 
nodeId=22efeb8f-176c-455a-b86a-9435f0bf0736, 
marsh=org.apache.ignite.internal.binary.BinaryMarshaller@521ec289, 
marshLocJobs=false, daemon=false, p2pEnabled=true, netTimeout=5000, 
sndRetryDelay=1000, sndRetryCnt=3, metricsHistSize=1, 
metricsUpdateFreq=2000, metricsExpTime=9223372036854775807, 
discoSpi=TcpDiscoverySpi [addrRslvr=null, sockTimeout=0, ackTimeout=0, 
marsh=null, reconCnt=10, reconDelay=2000, maxAckTimeout=60, 
forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null], 
segPlc=STOP, segResolveAttempts=2, waitForSegOnStart=true, 
allResolversPassReq=true, segChkFreq=1, commSpi=TcpCommunicationSpi 
[connectGate=null, connPlc=null, enableForcibleNodeKill=false, 
enableTroubleshootingLog=false, 
srvLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2@713e5835, 
locAddr=null, locHost=null, locPort=47100, locPortRange=100, shmemPort=-1, 
directBuf=true, directSndBuf=false, idleConnTimeout=60, connTimeout=5000, 
maxConnTimeout=60, reconCnt=10, sockSndBuf=32768, sockRcvBuf=32768, 
msgQueueLimit=0, slowClientQueueLimit=0, nioSrvr=null, shmemSrv=null, 
usePairedConnections=false, connectionsPerNode=1, tcpNoDelay=true, 
filterReachableAddresses=false, ackSndThreshold=32, unackedMsgsBufSize=0, 
sockWriteTimeout=2000, lsnr=null, boundTcpPort=-1, boundTcpShmemPort=-1, 
selectorsCnt=4, selectorSpins=0, addrRslvr=null, 
ctxInitLatch=java.util.concurrent.CountDownLatch@ec81a8f[Count = 1], 
stopping=false, 
metricsLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationMetricsListener@7132fdff],
 evtSpi=org.apache.ignite.spi.eventstorage.NoopEventStorageSpi@559c63da, 
colSpi=NoopCollisionSpi [], deploySpi=LocalDeploymentSpi [lsnr=null], 
indexingSpi=org.apache.ignite.spi.indexing.noop.NoopIndexingSpi@566066ac, 
addrRslvr=null, clientMode=true, rebalanceThreadPoolSize=1, 
txCfg=org.apache.ignite.configuration.TransactionConfiguration@1832128d, 
cacheSanityCheckEnabled=true, discoStartupDelay=6, deployMode=SHARED, 
p2pMissedCacheSize=100, locHost=null, timeSrvPortBase=31100, 
timeSrvPortRange=100, failureDetectionTimeout=1, 
clientFailureDetectionTimeout=3, metricsLogFreq=6, hadoopCfg=null, 
connectorCfg=org.apache.ignite.configuration.ConnectorConfiguration@7e89c971, 
odbcCfg=null, warmupClos=null, atomicCfg=AtomicConfiguration 

Re: Cache stats like number of cache hits, misses, reads, write, avg

2018-10-24 Thread Naveen
I guess I was doing the same.
Only change I could see is, you were enabling setMetrcis for both regionCfg
and storageCng

   regionCfg.setMetricsEnabled(true);
// Setting the data region configuration.
storageCfg.setDataRegionConfigurations(regionCfg);
storageCfg.setMetricsEnabled(true);

I have attached, wont be able to upload the files..

But here the content, server-config.xml we use to start the Ignite node
Begin serve XML ===

http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:util="http://www.springframework.org/schema/util;
xsi:schemaLocation="http://www.springframework.org/schema/beans 
  
http://www.springframework.org/schema/beans/spring-beans.xsd
   
http://www.springframework.org/schema/util   
http://www.springframework.org/schema/util/spring-util.xsd;>





























































End serve XML ===

XML used for creating the cache where metric enabled flag is set at cache
level.


Begin 


http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:util="http://www.springframework.org/schema/util;
xsi:schemaLocation="http://www.springframework.org/schema/beans
  
http://www.springframework.org/schema/beans/spring-beans.xsd
   http://www.springframework.org/schema/util
  
http://www.springframework.org/schema/util/spring-util.xsd;>

 

 











































partyId






















 







End  

Please let me know if you need anything further to reproduce the issue

Thanks



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


Re: How to configure service deployment as cluster node singleton in Ignite Configuration file?

2018-10-24 Thread Ilya Kasnacheev
Hello!

I'll go with totalCount=1.

Can you provide logs where service is run on more than one node?

Regards,
-- 
Ilya Kasnacheev


вт, 16 окт. 2018 г. в 10:22, the_palakkaran :

> Hi,
>
> I have a service that needs to be deployed in a cluster of three nodes. But
> I want only one node to run it. How can I restrict it? I have tried
> setting
>
> 1)maxPerNodeCount=1 and totalCount=1
> 2)totalCount=1
>
> Still on all nodes the service is getting run.
>
> Also, what is the equivalent to services.deployClusterSingleton() in
> IgniteConfigruation.xml?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: odbc 2.7 columns issue

2018-10-24 Thread Ilya Kasnacheev
Hello!

Can you also share your tables/caches configuration?

Regards,
-- 
Ilya Kasnacheev


ср, 24 окт. 2018 г. в 18:14, Igor Sapego :

> Hi,
>
> Can you share an ODBC log please?
>
> Best Regards,
> Igor
>
>
> On Wed, Oct 24, 2018 at 5:59 PM wt  wrote:
>
>> Hi
>>
>> Thank you for fixing the bug where in Excel i was not able to see the
>> tables. I can now however there are no columns visible and it gives an
>> error
>> that the data source did not return any columns. So it is a bit better
>> that
>> we can see the tables but we still cannot browse them and have to run a
>> select on the table to get the data back. I tried to get an odbc log but
>> nothing is logged. here is a screenshot 2018-10-24_15-58-35.png
>> <
>> http://apache-ignite-users.70518.x6.nabble.com/file/t1892/2018-10-24_15-58-35.png>
>>
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>


Re: odbc 2.7 columns issue

2018-10-24 Thread Igor Sapego
Hi,

Can you share an ODBC log please?

Best Regards,
Igor


On Wed, Oct 24, 2018 at 5:59 PM wt  wrote:

> Hi
>
> Thank you for fixing the bug where in Excel i was not able to see the
> tables. I can now however there are no columns visible and it gives an
> error
> that the data source did not return any columns. So it is a bit better that
> we can see the tables but we still cannot browse them and have to run a
> select on the table to get the data back. I tried to get an odbc log but
> nothing is logged. here is a screenshot 2018-10-24_15-58-35.png
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t1892/2018-10-24_15-58-35.png>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: npe: Failed to reinitialize local partition

2018-10-24 Thread Ilya Kasnacheev
Hello!

Can you make a simple reproducer of that problem?

I have tried to reproduce it but could not observe the backup number
changing. Instead, on 2.7 I observe correct number and on 2.6- I observe
NPE since cache2a does not exist in the grid.

Note that if you run ignite.getOrCreateCache("cache2a") then of course the
cache will be created with zero backups (default configuration). Avoid
doing that.

Regards,
-- 
Ilya Kasnacheev


вт, 23 окт. 2018 г. в 11:53, wangsan :

> Tks!
> I applyed the patch from the issue.And the NPE was fixed.
> But another problems happen:
>
> As the issue says:
> Steps to reproduce:
> Ignite server
>
> region1 (with persistence)
> region2 (without persistence)
> client
>
> cache1a from region1 – with custom affinity
> cache2a fom region2 – with custom affinity  !!! set backups=2(diff from the
> issule)
>
> 1. Populate data in both cache1a and cache2a.
> 2. Restart ignite server. It knows about cache1a from the persistent store.
> It doesn’t know about cache2a.
> 3. Don't restart client.Wait for the client to reconnect. Then the cache2a
> basckup will be 0 not 2!
>
> It looks like client reconnect did not carry cacheconfiguration(backups=2)
> but just use cacheName
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: Cache stats like number of cache hits, misses, reads, write, avg

2018-10-24 Thread aealexsandrov
Hi,

I tested that it works. I attached my code for the server node and
configuration for the visor.

Could you please check it?

startActivate.java
  
default-config.xml
  

Run main class from startActivate.java and  visor cmd with provided config.
As a result I see:

visor> cache -c=cacheNam -a
Time of the snapshot: 2018-10-24 18:03:38
++
|Name(@)|Mode | Nodes |   Entries (Heap / Off-heap)   |   
Hits |  Misses   |Reads|Writes|
++
| cacheNam(@c0) | PARTITIONED | 1 | min: 1000 (0 / 1000)  | min:
672| min: 0| min: 672| min: 1000|
|   | |   | avg: 1000.00 (0.00 / 1000.00) | avg:
672.00 | avg: 0.00 | avg: 672.00 | avg: 1000.00 |
|   | |   | max: 1000 (0 / 1000)  | max:
672| max: 0| max: 672| max: 1000|
++

Cache 'cacheNam(@c0)':
+-+
| Name(@) | cacheNam(@c0) |
| Nodes   | 1 |
| Total size Min/Avg/Max  | 1000 / 1000.00 / 1000 |
|   Heap size Min/Avg/Max | 0 / 0.00 / 0  |
|   Off-heap size Min/Avg/Max | 1000 / 1000.00 / 1000 |
+-+

Nodes for: cacheNam(@c0)
++
| Node ID8(@), IP  | CPUs | Heap Used | CPU Load |   Up Time|   
 
Size | Hi/Mi/Rd/Wr |
++
| 543734D6(@n0), 10.0.75.1 | 4| 1.89 %| 0.00 %   | 00:11:32.856 |
Total: 1000  | Hi: 672 |
|  |  |   |  |  |  
Heap: 0| Mi: 0   |
|  |  |   |  |  |  
Off-Heap: 1000 | Rd: 672 |
|  |  |   |  |  |  
Off-Heap Memory: 0 | Wr: 1000|
++
'Hi' - Number of cache hits.
'Mi' - Number of cache misses.
'Rd' - number of cache reads.
'Wr' - Number of cache writes.

Aggregated queries metrics:
  Minimum execution time: 00:00:00.000
  Maximum execution time: 00:00:00.000
  Average execution time: 00:00:00.000
  Total number of executions: 0
  Total number of failures:   0

Please check it and if it will work then try to check your config (or attach
it as a XML file because you provide only part of it).

BR,
Andrei



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


Re: 2.7 (.net) JavaException: class org.apache.ignite.binary.BinaryObjectException: Invalid flag value: 0

2018-10-24 Thread wt
hi please ignore the issue has been resolved by getting the latest from the
nightly build



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


odbc 2.7 columns issue

2018-10-24 Thread wt
Hi

Thank you for fixing the bug where in Excel i was not able to see the
tables. I can now however there are no columns visible and it gives an error
that the data source did not return any columns. So it is a bit better that
we can see the tables but we still cannot browse them and have to run a
select on the table to get the data back. I tried to get an odbc log but
nothing is logged. here is a screenshot 2018-10-24_15-58-35.png

  



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


Re: 2.7 (.net) JavaException: class org.apache.ignite.binary.BinaryObjectException: Invalid flag value: 0

2018-10-24 Thread akurbanov
Hello,

One thing, since 2.7 is not released, could you please point out when did
you get 2.7, what was the latest commit?

Regards,
Anton



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


Re: BufferUnderflowException on GridRedisProtocolParser

2018-10-24 Thread Michael Fong
Hi Stan,

Thanks for the suggestion.

I have tried to patch it, which would work 95% of the case, but would run
into another random issue. I have mailed dev list for suggestions.


Regards,

Michael

On Thu, Oct 11, 2018 at 7:10 PM Stanislav Lukyanov 
wrote:

> Well, you need to wait for the IGNITE-7153 fix then.
>
> Or contribute it! :)
>
> I checked the code, and it seems to be a relatively easy fix. One needs to
> alter the GridRedisProtocolParser
>
> to use ParserState in the way GridTcpRestParser::parseMemcachePacker does.
>
>
>
> Stan
>
>
>
> *From: *Michael Fong 
> *Sent: *11 октября 2018 г. 7:15
> *To: *user@ignite.apache.org
> *Subject: *Re: BufferUnderflowException on GridRedisProtocolParser
>
>
>
> Hi,
>
>
>
> The symptom seems very likely to IGNITE-7153, where the default tcp send
> buffer on that environment happens to be 4096
>
> [root]# cat /proc/sys/net/ipv4/tcp_wmem
>
> 4096
>
>
>
> Regards,
>
>
>
> On Thu, Oct 11, 2018 at 10:56 AM Michael Fong 
> wrote:
>
> Hi,
>
>
>
> Thank you for your response. Not to every request; we only see this for
> some specific ones - when elCnt (4270) > buf.limit (4096).  We are trying
> to narrowing down the data set to find the root cause.
>
>
>
> Thanks.
>
>
>
> Regards,
>
>
>
> On Thu, Oct 11, 2018 at 12:08 AM Ilya Kasnacheev <
> ilya.kasnach...@gmail.com> wrote:
>
> Hello!
>
>
>
> Do you see this error on every request, or on some specific ones?
>
>
>
> Regards,
>
> --
>
> Ilya Kasnacheev
>
>
>
>
>
> вт, 9 окт. 2018 г. в 15:54, Michael Fong :
>
> Hi, all
>
>
>
> We are evaluating Ignite compatibility with Redis protocol, and we hit an
> issue as the following:
>
> Does the stacktrace look a bit like IGNITE-7153?
>
>
>
> java.nio.BufferUnderflowException
>
> at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
>
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:111)
>
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readArray(GridRedisProtocolParser.java:86)
>
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:165)
>
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:72)
>
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
>
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
>
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3490)
>
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
>
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1113)
>
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2339)
>
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2110)
>
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1764)
>
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>
> at java.lang.Thread.run(Thread.java:745)
>
> [2018-10-09
> 12:45:49,946][ERROR][grid-nio-worker-tcp-rest-1-#37][GridTcpRestProtocol]
> Closing NIO session because of unhandled exception.
>
> class org.apache.ignite.internal.util.nio.GridNioException: null
>
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2365)
>
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2110)
>
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1764)
>
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>
> at java.lang.Thread.run(Thread.java:745)
>
>
>
>
>


Re: ignite odbc build error

2018-10-24 Thread wt
hi

Thank you it is all resolved now using the nightly build including the odbc
and i can now see the odbc tables from Excel. fabulous



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


Re: where to download 2.7 source

2018-10-24 Thread wt
hi

Thank you it is all resolved now using the nightly build including the odbc
and i can now see the odbc tables from Excel. fabulous



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


Re: where to download 2.7 source

2018-10-24 Thread wt
i am giving the nightly builds a go and will use those in the .net proj
reference. Fingers crossed  - been struggling on this all day so far and
feel very demotivated.



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


Re: ignite odbc build error

2018-10-24 Thread wt
omg you are a life saver

I CAN'T THANK YOU ENOUGH :)



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


Re: where to download 2.7 source

2018-10-24 Thread Ilya Kasnacheev
Hello!

Have you tried to run Apache.Ignite.exe from your build's platforms/dotnet?
Does it run? Have you also tried nightly build?

I suspect that your project reference to 2.7 might be incorrect if you can
get server .Net nodes to start.

Regards,
-- 
Ilya Kasnacheev


ср, 24 окт. 2018 г. в 15:59, wt :

> I believe i have done this.
>
>
> I have downloaded 2.7 from github. packaged it with maven and then copied
> the entire dir to my local windows pc. I then updated the IGNITE_HOME
> variable to point to this new location. I started the server using the bat
> file (i couldnt start it in a .net proj as it was throwing the same error)
>
> In the .net project i deleted the references to 2.6 and added the
> references
> to 2.7
>
> I think i covered everything.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: ignite odbc build error

2018-10-24 Thread Ilya Kasnacheev
Hello!

Have you tried Nightly Builds?

https://ci.ignite.apache.org/viewLog.html?buildId=lastSuccessful=Releases_NightlyRelease_RunApacheIgniteNightlyRelease=artifacts=1#!-oll7z3tvqsdk,-1fllqn9a26ew6,1e6erfmy67dj4,enpgjwyte3hs

apache-ignite-2.7.0.20181024-bin.zip

has platforms /

cpp /

bin /

odbc /

 ignite-odbc-amd64.msi


Regards,
-- 
Ilya Kasnacheev


ср, 24 окт. 2018 г. в 15:55, wt :

> hi
>
> The problem i have is this. Next week Friday (2nd) i am showcasing Ignite
> to
> the COO of a major exchange and part of this demo will be to show opening
> Excel and browsing the tables in ignite through the odbc. Unfortunately in
> 2.6 (i am not sure of prev versions) there is a bug in the odbc driver that
> prevents tables from being browsable  (
> https://issues.apache.org/jira/browse/IGNITE-9891 ). So the fix has been
> added to 2.7 but i am unable to build these drivers on windows so a major
> part of the demo is now likely going to result in Ignite being binned (our
> COO doesn't give second chances so it has to be right the first time).
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: where to download 2.7 source

2018-10-24 Thread wt
I believe i have done this.


I have downloaded 2.7 from github. packaged it with maven and then copied
the entire dir to my local windows pc. I then updated the IGNITE_HOME
variable to point to this new location. I started the server using the bat
file (i couldnt start it in a .net proj as it was throwing the same error)

In the .net project i deleted the references to 2.6 and added the references
to 2.7

I think i covered everything.



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


Re: where to download 2.7 source

2018-10-24 Thread Ilya Kasnacheev
Hello!

This error looks exactly like the one you're getting when running
mismatching version of .Net versus Java.

So I assume that either Java libraries used by your project are not 2.7 or
.Net is really not.

You could specify path to your Java portion of Apache Ignite by specifying
IGNITE_HOME environment variable or by specifying
IgniteConfiguration.IgniteHome
on .Net side.

Regards,
-- 
Ilya Kasnacheev


ср, 24 окт. 2018 г. в 13:29, wt :

> Hi Igor
>
> Not sure if there is something missing in the .net ignite side for 2.7
>
> I have built 2.7 on a linux machine, copied it to my windows machine and
> can
> launch it from the ignite.bat file no problem. I built the dotnet source as
> well and referenced those in my current project (a winforms app). When the
> client starts up it throws this
>
> Apache.Ignite.Core.Binary.BinaryObjectException
>   HResult=0x80131500
>   Message=Invalid flag value: 0
>   Source=Apache.Ignite.Core
>   StackTrace:
>at Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg) in
>
> C:\Users\ww309\Downloads\ignite.dotnet.2.7\Apache.Ignite.Core\Ignition.cs:line
> 323
>at ClusterTool.classes.IgniteClient.StartClient() in
> C:\temp\IgniteTool\ClusterTool\classes\IgniteClient.cs:line 24
>at System.Threading.ExecutionContext.RunInternal(ExecutionContext
> executionContext, ContextCallback callback, Object state, Boolean
> preserveSyncCtx)
>at System.Threading.ExecutionContext.Run(ExecutionContext
> executionContext, ContextCallback callback, Object state, Boolean
> preserveSyncCtx)
>at System.Threading.ExecutionContext.Run(ExecutionContext
> executionContext, ContextCallback callback, Object state)
>at System.Threading.ThreadHelper.ThreadStart()
>
> Inner Exception 1:
> JavaException: class org.apache.ignite.binary.BinaryObjectException:
> Invalid
> flag value: 0
> at
>
> org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1989)
> at
>
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readObjectDetached(BinaryReaderExImpl.java:1334)
> at
>
> org.apache.ignite.internal.processors.platform.utils.PlatformConfigurationUtils.readIgniteConfiguration(PlatformConfigurationUtils.java:627)
> at
>
> org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetConfigurationClosure.processPrepareResult(PlatformDotNetConfigurationClosure.java:199)
> at
>
> org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetConfigurationClosure.prepare(PlatformDotNetConfigurationClosure.java:186)
> at
>
> org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetConfigurationClosure.apply0(PlatformDotNetConfigurationClosure.java:113)
> at
>
> org.apache.ignite.internal.processors.platform.PlatformAbstractConfigurationClosure.apply(PlatformAbstractConfigurationClosure.java:50)
> at
>
> org.apache.ignite.internal.processors.platform.PlatformAbstractConfigurationClosure.apply(PlatformAbstractConfigurationClosure.java:27)
> at
>
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:40)
> at
>
> org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:75)
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: ignite odbc build error

2018-10-24 Thread Ilya Kasnacheev
Hello!

Unfortunately I did not see in your email the exact error that you are
seeing. However I think that Apache Ignite 2.7 Release Candidate will be
available any day now.

Regards,
-- 
Ilya Kasnacheev


ср, 24 окт. 2018 г. в 15:31, wt :

> ok i didnt realise that. Could you please help me understand why i am
> getting
> that error when following the exact instructions on
>
> https://apacheignite.readme.io/docs/odbc-driver
>
>
>
> *Building installers on Windows*
>
> /Once you have built driver binaries you may want to build installers for
> easier installation. Ignite uses WiX Toolset to generate ODBC installers,
> so
> to build them you'll need to download and install WiX. Make sure you have
> added bin directory of the WiX Toolset to your PATH variable.
>
> Once everything is ready, open terminal and navigate to the directory
> %IGNITE_HOME%\platforms\cpp\odbc\install. Execute the following commands
> one
> by one to build drivers:
>
> 64-bit driver
> 32-bit driver
>
> candle.exe ignite-odbc-x86.wxs
> light.exe -ext WixUIExtension ignite-odbc-x86.wixobj
>
> candle.exe ignite-odbc-x86.wxs
> light.exe -ext WixUIExtension ignite-odbc-x86.wixobj/
>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: ignite odbc build error

2018-10-24 Thread wt
maybe you could provide me with the 2.7 ignite.odbc.dll and i can skip the
build part in visual studio and run

light.exe -ext WixUIExtension ignite-odbc-x86.wixobj



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


Re: ignite odbc build error

2018-10-24 Thread wt
ok i didnt realise that. Could you please help me understand why i am getting
that error when following the exact instructions on 

https://apacheignite.readme.io/docs/odbc-driver



*Building installers on Windows*

/Once you have built driver binaries you may want to build installers for
easier installation. Ignite uses WiX Toolset to generate ODBC installers, so
to build them you'll need to download and install WiX. Make sure you have
added bin directory of the WiX Toolset to your PATH variable.

Once everything is ready, open terminal and navigate to the directory
%IGNITE_HOME%\platforms\cpp\odbc\install. Execute the following commands one
by one to build drivers:

64-bit driver
32-bit driver

candle.exe ignite-odbc-x86.wxs
light.exe -ext WixUIExtension ignite-odbc-x86.wixobj

candle.exe ignite-odbc-x86.wxs
light.exe -ext WixUIExtension ignite-odbc-x86.wixobj/






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


Re: ignite odbc build error

2018-10-24 Thread Ilya Kasnacheev
Hello!

I hope you understand that you're not getting a Windows redistributable of
ODBC driver by building on Linux? You will only build Linux ODBC driver
that way.

Regards,
-- 
Ilya Kasnacheev


ср, 24 окт. 2018 г. в 15:06, wt :

> i do. this is a major blocker for me for my demo to the COO. All i am
> looking
> for is the 32bit odbc msi. is there anywhere i can get it or if you know if
> i should be using a different version of linux
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: ignite odbc build error

2018-10-24 Thread wt
i do. this is a major blocker for me for my demo to the COO. All i am looking
for is the 32bit odbc msi. is there anywhere i can get it or if you know if
i should be using a different version of linux




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


2.7 (.net) JavaException: class org.apache.ignite.binary.BinaryObjectException: Invalid flag value: 0

2018-10-24 Thread wt
Not sure if there is something missing in the .net ignite side for 2.7

I have built 2.7 on a linux machine, copied it to my windows machine and can
launch it from the ignite.bat file no problem. I built the dotnet source as
well and referenced those in my current project (a winforms app). When the
client starts up it throws this

Apache.Ignite.Core.Binary.BinaryObjectException
  HResult=0x80131500
  Message=Invalid flag value: 0
  Source=Apache.Ignite.Core
  StackTrace:
   at Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg) in
C:\Users\ww309\Downloads\ignite.dotnet.2.7\Apache.Ignite.Core\Ignition.cs:line
323
   at ClusterTool.classes.IgniteClient.StartClient() in
C:\temp\IgniteTool\ClusterTool\classes\IgniteClient.cs:line 24
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

Inner Exception 1:
JavaException: class org.apache.ignite.binary.BinaryObjectException: Invalid
flag value: 0
at
org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1989)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.readObjectDetached(BinaryReaderExImpl.java:1334)
at
org.apache.ignite.internal.processors.platform.utils.PlatformConfigurationUtils.readIgniteConfiguration(PlatformConfigurationUtils.java:627)
at
org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetConfigurationClosure.processPrepareResult(PlatformDotNetConfigurationClosure.java:199)
at
org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetConfigurationClosure.prepare(PlatformDotNetConfigurationClosure.java:186)
at
org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetConfigurationClosure.apply0(PlatformDotNetConfigurationClosure.java:113)
at
org.apache.ignite.internal.processors.platform.PlatformAbstractConfigurationClosure.apply(PlatformAbstractConfigurationClosure.java:50)
at
org.apache.ignite.internal.processors.platform.PlatformAbstractConfigurationClosure.apply(PlatformAbstractConfigurationClosure.java:27)
at
org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:40)
at
org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:75)





here is the place it throws this error


public static IIgnite Start(IgniteConfiguration cfg)
{
IgniteArgumentCheck.NotNull(cfg, "cfg");

cfg = new IgniteConfiguration(cfg);  // Create a copy so that
config can be modified and reused.

lock (SyncRoot)
{
// 0. Init logger
var log = cfg.Logger ?? new JavaLogger();

log.Debug("Starting Ignite.NET " +
Assembly.GetExecutingAssembly().GetName().Version);

// 1. Check GC settings.
CheckServerGc(cfg, log);

// 2. Create context.
JvmDll.Load(cfg.JvmDllPath, log);

var cbs = IgniteManager.CreateJvmContext(cfg, log);
var env = cbs.Jvm.AttachCurrentThread();
log.Debug("JVM started.");

var gridName = cfg.IgniteInstanceName;

if (cfg.AutoGenerateIgniteInstanceName)
{
gridName = (gridName ?? "ignite-instance-") +
Guid.NewGuid();
}

// 3. Create startup object which will guide us through the
rest of the process.
_startup = new Startup(cfg, cbs);

PlatformJniTarget interopProc = null;

try
{
// 4. Initiate Ignite start.
UU.IgnitionStart(env, cfg.SpringConfigUrl, gridName,
ClientMode, cfg.Logger != null, cbs.IgniteId,
cfg.RedirectJavaConsoleOutput);

// 5. At this point start routine is finished. We expect
STARTUP object to have all necessary data.
var node = _startup.Ignite;
interopProc = (PlatformJniTarget)node.InteropProcessor;

var javaLogger = log as JavaLogger;
if (javaLogger != null)
{
javaLogger.SetIgnite(node);
}

// 6. On-start callback (notify lifecycle components).
node.OnStart();

Nodes[new NodeKey(_startup.Name)] = node;

return node;
}
catch (Exception ex)
{
// 1. Perform keys cleanup.

Re: ignite odbc build error

2018-10-24 Thread Igor Sapego
No, I've never seen this error before. Seems like
some issue in configuration of your OS.

Do you have pkg-config installed?

Best Regards,
Igor


On Wed, Oct 24, 2018 at 2:17 PM wt  wrote:

> those errors are gone but it looks like some ubuntu issue is now a problem.
> Have you seen this before?
>
> ubuntu@ip-10-112-47-3:/ignite2.7/ignite/modules/platforms/cpp$ libtoolize
> &&
> aclocal && autoheader && automake --add-missing && autoreconf ./configure
> --enable-odbc --disable-node --disable-core
> Useless use of /d modifier in transliteration operator at
> /usr/share/automake-1.9/Automake/Wrap.pm line 60.
> autoreconf: 'configure.ac' or 'configure.in' is required
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: Cache stats like number of cache hits, misses, reads, write, avg

2018-10-24 Thread aealexsandrov
Hi,

Could you please provide the full configuration of the node?

BR,
Andrei



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


Re: ignite odbc build error

2018-10-24 Thread wt
those errors are gone but it looks like some ubuntu issue is now a problem.
Have you seen this before?

ubuntu@ip-10-112-47-3:/ignite2.7/ignite/modules/platforms/cpp$ libtoolize &&
aclocal && autoheader && automake --add-missing && autoreconf ./configure
--enable-odbc --disable-node --disable-core
Useless use of /d modifier in transliteration operator at
/usr/share/automake-1.9/Automake/Wrap.pm line 60.
autoreconf: 'configure.ac' or 'configure.in' is required




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


Cache stats like number of cache hits, misses, reads, write, avg

2018-10-24 Thread Naveen
Hi

We are using Ignite 2.5/2.6

Have enables stats collection by setting this property 



Created cache, and ran some Gets on it, and when we check stats thru visor,
we dont see any stats for read

cache -c=CustomerCache -a

All the columns like Hits, Writes, Reads are showing as zero, is there
anything we should do to capture stats.

Thanks



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


Re: ignite odbc build error

2018-10-24 Thread Igor Sapego
Try removing AM_PROG_AR as well. I will fix the issue in future.


Best Regards,
Igor


On Wed, Oct 24, 2018 at 1:41 PM wt  wrote:

> Hi Igor
>
> *I tried as a standard user and i get this*
>
> ubuntu@ip-10-112-47-3:/ignite2.7/ignite/modules/platforms/cpp$  libtoolize
> && aclocal && autoheader && automake --add-missing && autoreconf
> ./configure.ac --enable-odbc --disable-node --disable-core
> aclocal:configure.ac:32: warning: macro `AM_SILENT_RULES' not found in
> library
> aclocal:configure.ac:36: warning: macro `AM_PROG_AR' not found in library
> Useless use of /d modifier in transliteration operator at
> /usr/share/automake-1.9/Automake/Wrap.pm line 60.
> aclocal:configure.ac:32: warning: macro `AM_SILENT_RULES' not found in
> library
> aclocal:configure.ac:36: warning: macro `AM_PROG_AR' not found in library
> configure.ac:32: error: possibly undefined macro: AM_SILENT_RULES
>   If this token and others are legitimate, please use m4_pattern_allow.
>   See the Autoconf documentation.
> configure.ac:36: error: possibly undefined macro: AM_PROG_AR
> autoreconf: /usr/bin/autoconf failed with exit status: 1
>
>
>
> *I then tried removing that line from the file and i get this*
>
> ubuntu@ip-10-112-47-3:/ignite2.7/ignite/modules/platforms/cpp$ libtoolize
> &&
> aclocal && autoheader && automake --add-missing && autoreconf ./
> configure.ac
> --enable-odbc --disable-node --disable-core
> aclocal:configure.ac:36: warning: macro `AM_PROG_AR' not found in library
> Useless use of /d modifier in transliteration operator at
> /usr/share/automake-1.9/Automake/Wrap.pm line 60.
> aclocal:configure.ac:36: warning: macro `AM_PROG_AR' not found in library
> configure.ac:36: error: possibly undefined macro: AM_PROG_AR
>   If this token and others are legitimate, please use m4_pattern_allow.
>   See the Autoconf documentation.
> autoreconf: /usr/bin/autoconf failed with exit status: 1
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: ignite odbc build error

2018-10-24 Thread wt
Hi Igor

*I tried as a standard user and i get this*

ubuntu@ip-10-112-47-3:/ignite2.7/ignite/modules/platforms/cpp$  libtoolize
&& aclocal && autoheader && automake --add-missing && autoreconf
./configure.ac --enable-odbc --disable-node --disable-core
aclocal:configure.ac:32: warning: macro `AM_SILENT_RULES' not found in
library
aclocal:configure.ac:36: warning: macro `AM_PROG_AR' not found in library
Useless use of /d modifier in transliteration operator at
/usr/share/automake-1.9/Automake/Wrap.pm line 60.
aclocal:configure.ac:32: warning: macro `AM_SILENT_RULES' not found in
library
aclocal:configure.ac:36: warning: macro `AM_PROG_AR' not found in library
configure.ac:32: error: possibly undefined macro: AM_SILENT_RULES
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.
configure.ac:36: error: possibly undefined macro: AM_PROG_AR
autoreconf: /usr/bin/autoconf failed with exit status: 1



*I then tried removing that line from the file and i get this*

ubuntu@ip-10-112-47-3:/ignite2.7/ignite/modules/platforms/cpp$ libtoolize &&
aclocal && autoheader && automake --add-missing && autoreconf ./configure.ac
--enable-odbc --disable-node --disable-core
aclocal:configure.ac:36: warning: macro `AM_PROG_AR' not found in library
Useless use of /d modifier in transliteration operator at
/usr/share/automake-1.9/Automake/Wrap.pm line 60.
aclocal:configure.ac:36: warning: macro `AM_PROG_AR' not found in library
configure.ac:36: error: possibly undefined macro: AM_PROG_AR
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1





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


Re: where to download 2.7 source

2018-10-24 Thread wt
Hi Igor

Not sure if there is something missing in the .net ignite side for 2.7

I have built 2.7 on a linux machine, copied it to my windows machine and can
launch it from the ignite.bat file no problem. I built the dotnet source as
well and referenced those in my current project (a winforms app). When the
client starts up it throws this

Apache.Ignite.Core.Binary.BinaryObjectException
  HResult=0x80131500
  Message=Invalid flag value: 0
  Source=Apache.Ignite.Core
  StackTrace:
   at Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg) in
C:\Users\ww309\Downloads\ignite.dotnet.2.7\Apache.Ignite.Core\Ignition.cs:line
323
   at ClusterTool.classes.IgniteClient.StartClient() in
C:\temp\IgniteTool\ClusterTool\classes\IgniteClient.cs:line 24
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

Inner Exception 1:
JavaException: class org.apache.ignite.binary.BinaryObjectException: Invalid
flag value: 0
at
org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1989)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.readObjectDetached(BinaryReaderExImpl.java:1334)
at
org.apache.ignite.internal.processors.platform.utils.PlatformConfigurationUtils.readIgniteConfiguration(PlatformConfigurationUtils.java:627)
at
org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetConfigurationClosure.processPrepareResult(PlatformDotNetConfigurationClosure.java:199)
at
org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetConfigurationClosure.prepare(PlatformDotNetConfigurationClosure.java:186)
at
org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetConfigurationClosure.apply0(PlatformDotNetConfigurationClosure.java:113)
at
org.apache.ignite.internal.processors.platform.PlatformAbstractConfigurationClosure.apply(PlatformAbstractConfigurationClosure.java:50)
at
org.apache.ignite.internal.processors.platform.PlatformAbstractConfigurationClosure.apply(PlatformAbstractConfigurationClosure.java:27)
at
org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:40)
at
org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:75)





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


Re: where to download 2.7 source

2018-10-24 Thread wt
thanks Igor

Unfortunately i have a demo next week and i need the odbc bug that was fixed
in 2.7 to be ready for the demo so i have no choice but to try use the
current status of 2.7.

Thanks for the info



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


ignite odbc build error

2018-10-24 Thread wt
i am trying to build the 2.7 odbc driver and i am getting an error. I am
using ubuntu 14

root@ip-10-112-47-3:/ignite2.7/ignite/modules/platforms/cpp# ls
aclocal.m4  config.sub   cpp.dxg   jni missing
thin-client
autom4te.cache  configuredepcomp   ltmain.sh   odbc   
thin-client-test
binary  configure.ac DEVNOTES.txt  m4  odbc-test
common  configure.acrel  examples  Makefile.am project
config.guesscore igniteMakefile.amrel  README.md
config.h.in core-testinstall-shMakefile.in README.txt


root@ip-10-112-47-3:/ignite2.7/ignite/modules/platforms/cpp# libtoolize &&
aclocal && autoheader && automake --add-missing && autoreconf ./configure.ac
--enable-odbc --disable-node --disable-core
aclocal:configure.ac:32: warning: macro `AM_SILENT_RULES' not found in
library
aclocal:configure.ac:36: warning: macro `AM_PROG_AR' not found in library
Useless use of /d modifier in transliteration operator at
/usr/share/automake-1.9/Automake/Wrap.pm line 60.
aclocal:configure.ac:32: warning: macro `AM_SILENT_RULES' not found in
library
aclocal:configure.ac:36: warning: macro `AM_PROG_AR' not found in library
configure.ac:32: error: possibly undefined macro: AM_SILENT_RULES
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.
configure.ac:36: error: possibly undefined macro: AM_PROG_AR
autoreconf: /usr/bin/autoconf failed with exit status: 1
root@ip-10-112-47-3:/ignite2.7/ignite/modules/platforms/cpp#




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


Re: where to download 2.7 source

2018-10-24 Thread Igor Sapego
Hello,

2.7 is not released yet, but you can get code from git repository
from the ignite-2.7 branch. Note however that there are still some
issues/missing features in this branch. You can see the current
state of the release in the appropriate thread on the devlist.

[1] - https://github.com/apache/ignite/tree/ignite-2.7

Best Regards,
Igor


On Wed, Oct 24, 2018 at 10:57 AM wt  wrote:

> I am doing a demo to our COO next week and part of this demo is excel
> ignite
> odbc which in 2.6 doesn't allow tables to be browsed see the following jira
>
> https://issues.apache.org/jira/browse/IGNITE-9891
>
> anyway I am struggling to find if there is an available source with the
> latest builds to test.
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


RE: OVER() clause in ignite

2018-10-24 Thread Sriveena Mattaparthi
Thanks Andrey…

Regards,
Sriveena

From: Andrey Mashenkov [mailto:andrey.mashen...@gmail.com]
Sent: Wednesday, October 24, 2018 1:07 PM
To: user@ignite.apache.org; Sriveena Mattaparthi
Subject: Re: OVER() clause in ignite

Hi,

Ignite have no support window functions due to lack of underlying H2.
OVER is a part of SQL ANSI'03 standart, but Ignite claims to be ANSI'99 
complaint.

The only workaround is to rewrite query with using joins or calculate result 
manually.
User aggregate functions also are not supported and we have no plans for this, 
see IGNITE-2177 [1].

There is ticket for Window-functions support IGNITE-6918 [2], but it is not 
planned to any future version for now.

[1] 
https://issues.apache.org/jira/browse/IGNITE-2177
[2] 
https://issues.apache.org/jira/browse/IGNITE-6918

On Wed, Oct 24, 2018 at 9:55 AM Sriveena Mattaparthi 
mailto:sriveena.mattapar...@ekaplus.com>> 
wrote:
Thanks Mikael..Could you please suggest any other alternative to achieve this?

Regards,
Sriveena

From: Mikael 
[mailto:mikael-arons...@telia.com]
Sent: Wednesday, October 24, 2018 11:47 AM
To: user@ignite.apache.org
Subject: Re: OVER() clause in ignite


Hi!

As far as I know H2 does not support OVER.
Mikael
Den 2018-10-24 kl. 07:28, skrev Sriveena Mattaparthi:
Do we support over() clause in SQL in ignite like
select count(*) over() totalrecords  from EMPLOYEE;

please confirm.

Thanks & Regards,
Sriveena

“Confidentiality Notice: The contents of this email message and any attachments 
are intended solely for the addressee(s) and may contain confidential and/or 
privileged information and may be legally protected from disclosure. If you are 
not the intended recipient of this message or their agent, or if this message 
has been addressed to you in error, please immediately alert the sender by 
reply email and then delete this message and any attachments. If you are not 
the intended recipient, you are hereby notified that any use, dissemination, 
copying, or storage of this message or its attachments is strictly prohibited.”

“Confidentiality Notice: The contents of this email message and any attachments 
are intended solely for the addressee(s) and may contain confidential and/or 
privileged information and may be legally protected from disclosure. If you are 
not the intended recipient of this message or their agent, or if this message 
has been addressed to you in error, please immediately alert the sender by 
reply email and then delete this message and any attachments. If you are not 
the intended recipient, you are hereby notified that any use, dissemination, 
copying, or storage of this message or its attachments is strictly prohibited.”


--
Best regards,
Andrey V. Mashenkov
“Confidentiality Notice: The contents of this email message and any attachments 
are intended solely for the addressee(s) and may contain confidential and/or 
privileged information and may be legally protected from disclosure. If you are 
not the intended recipient of this message or their agent, or if this message 
has been addressed to you in error, please immediately alert the sender by 
reply email and then delete this message and any attachments. If you are not 
the intended recipient, you are hereby notified that any use, dissemination, 
copying, or storage of this message or its attachments is strictly prohibited.”


Re: OVER() clause in ignite

2018-10-24 Thread wt
i noticed H2 roadmap for the current version has windowing functions. 

http://www.h2database.com/html/roadmap.html

i guess this will mean ignite will have it available in the near future?



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


where to download 2.7 source

2018-10-24 Thread wt
I am doing a demo to our COO next week and part of this demo is excel ignite
odbc which in 2.6 doesn't allow tables to be browsed see the following jira

https://issues.apache.org/jira/browse/IGNITE-9891

anyway I am struggling to find if there is an available source with the
latest builds to test.





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


Re: OVER() clause in ignite

2018-10-24 Thread Andrey Mashenkov
Hi,

Ignite have no support window functions due to lack of underlying H2.
OVER is a part of SQL ANSI'03 standart, but Ignite claims to be ANSI'99
complaint.

The only workaround is to rewrite query with using joins or calculate
result manually.
User aggregate functions also are not supported and we have no plans for
this, see IGNITE-2177 [1].

There is ticket for Window-functions support IGNITE-6918 [2], but it is not
planned to any future version for now.

[1] https://issues.apache.org/jira/browse/IGNITE-2177
[2] https://issues.apache.org/jira/browse/IGNITE-6918

On Wed, Oct 24, 2018 at 9:55 AM Sriveena Mattaparthi <
sriveena.mattapar...@ekaplus.com> wrote:

> Thanks Mikael..Could you please suggest any other alternative to achieve
> this?
>
>
>
> Regards,
>
> Sriveena
>
>
>
> *From:* Mikael [mailto:mikael-arons...@telia.com]
> *Sent:* Wednesday, October 24, 2018 11:47 AM
> *To:* user@ignite.apache.org
> *Subject:* Re: OVER() clause in ignite
>
>
>
> Hi!
>
> As far as I know H2 does not support OVER.
>
> Mikael
>
> Den 2018-10-24 kl. 07:28, skrev Sriveena Mattaparthi:
>
> Do we support over() clause in SQL in ignite like
>
> select count(*) over() totalrecords  from EMPLOYEE;
>
>
>
> please confirm.
>
>
>
> Thanks & Regards,
>
> Sriveena
>
>
>
> “Confidentiality Notice: The contents of this email message and any
> attachments are intended solely for the addressee(s) and may contain
> confidential and/or privileged information and may be legally protected
> from disclosure. If you are not the intended recipient of this message or
> their agent, or if this message has been addressed to you in error, please
> immediately alert the sender by reply email and then delete this message
> and any attachments. If you are not the intended recipient, you are hereby
> notified that any use, dissemination, copying, or storage of this message
> or its attachments is strictly prohibited.”
>
>
> “Confidentiality Notice: The contents of this email message and any
> attachments are intended solely for the addressee(s) and may contain
> confidential and/or privileged information and may be legally protected
> from disclosure. If you are not the intended recipient of this message or
> their agent, or if this message has been addressed to you in error, please
> immediately alert the sender by reply email and then delete this message
> and any attachments. If you are not the intended recipient, you are hereby
> notified that any use, dissemination, copying, or storage of this message
> or its attachments is strictly prohibited.”
>


-- 
Best regards,
Andrey V. Mashenkov


RE: OVER() clause in ignite

2018-10-24 Thread Sriveena Mattaparthi
Thanks Mikael

Regards,
Sriveena

From: Mikael [mailto:mikael-arons...@telia.com]
Sent: Wednesday, October 24, 2018 12:36 PM
To: user@ignite.apache.org
Subject: Re: OVER() clause in ignite


Hi!

I am not sure, but you might find something useful here:

https://stackoverflow.com/questions/6249449/is-h2-database-able-to-make-sql-query-of-the-over-clause-with-aggregate-function

Mikael

Den 2018-10-24 kl. 08:55, skrev Sriveena Mattaparthi:
Thanks Mikael..Could you please suggest any other alternative to achieve this?

Regards,
Sriveena

From: Mikael [mailto:mikael-arons...@telia.com]
Sent: Wednesday, October 24, 2018 11:47 AM
To: user@ignite.apache.org
Subject: Re: OVER() clause in ignite


Hi!

As far as I know H2 does not support OVER.
Mikael
Den 2018-10-24 kl. 07:28, skrev Sriveena Mattaparthi:
Do we support over() clause in SQL in ignite like
select count(*) over() totalrecords  from EMPLOYEE;

please confirm.

Thanks & Regards,
Sriveena

"Confidentiality Notice: The contents of this email message and any attachments 
are intended solely for the addressee(s) and may contain confidential and/or 
privileged information and may be legally protected from disclosure. If you are 
not the intended recipient of this message or their agent, or if this message 
has been addressed to you in error, please immediately alert the sender by 
reply email and then delete this message and any attachments. If you are not 
the intended recipient, you are hereby notified that any use, dissemination, 
copying, or storage of this message or its attachments is strictly prohibited."

"Confidentiality Notice: The contents of this email message and any attachments 
are intended solely for the addressee(s) and may contain confidential and/or 
privileged information and may be legally protected from disclosure. If you are 
not the intended recipient of this message or their agent, or if this message 
has been addressed to you in error, please immediately alert the sender by 
reply email and then delete this message and any attachments. If you are not 
the intended recipient, you are hereby notified that any use, dissemination, 
copying, or storage of this message or its attachments is strictly prohibited."

"Confidentiality Notice: The contents of this email message and any attachments 
are intended solely for the addressee(s) and may contain confidential and/or 
privileged information and may be legally protected from disclosure. If you are 
not the intended recipient of this message or their agent, or if this message 
has been addressed to you in error, please immediately alert the sender by 
reply email and then delete this message and any attachments. If you are not 
the intended recipient, you are hereby notified that any use, dissemination, 
copying, or storage of this message or its attachments is strictly prohibited."


Re: OVER() clause in ignite

2018-10-24 Thread Mikael

Hi!

I am not sure, but you might find something useful here:

https://stackoverflow.com/questions/6249449/is-h2-database-able-to-make-sql-query-of-the-over-clause-with-aggregate-function

Mikael


Den 2018-10-24 kl. 08:55, skrev Sriveena Mattaparthi:


Thanks Mikael..Could you please suggest any other alternative to 
achieve this?


Regards,

Sriveena

*From:*Mikael [mailto:mikael-arons...@telia.com]
*Sent:* Wednesday, October 24, 2018 11:47 AM
*To:* user@ignite.apache.org
*Subject:* Re: OVER() clause in ignite

Hi!

As far as I know H2 does not support OVER.

Mikael

Den 2018-10-24 kl. 07:28, skrev Sriveena Mattaparthi:

Do we support over() clause in SQL in ignite like

select count(*) over() totalrecords  from EMPLOYEE;

please confirm.

Thanks & Regards,

Sriveena

“Confidentiality Notice: The contents of this email message and
any attachments are intended solely for the addressee(s) and may
contain confidential and/or privileged information and may be
legally protected from disclosure. If you are not the intended
recipient of this message or their agent, or if this message has
been addressed to you in error, please immediately alert the
sender by reply email and then delete this message and any
attachments. If you are not the intended recipient, you are hereby
notified that any use, dissemination, copying, or storage of this
message or its attachments is strictly prohibited.”

“Confidentiality Notice: The contents of this email message and any 
attachments are intended solely for the addressee(s) and may contain 
confidential and/or privileged information and may be legally 
protected from disclosure. If you are not the intended recipient of 
this message or their agent, or if this message has been addressed to 
you in error, please immediately alert the sender by reply email and 
then delete this message and any attachments. If you are not the 
intended recipient, you are hereby notified that any use, 
dissemination, copying, or storage of this message or its attachments 
is strictly prohibited.” 




RE: OVER() clause in ignite

2018-10-24 Thread Sriveena Mattaparthi
Thanks Mikael..Could you please suggest any other alternative to achieve this?

Regards,
Sriveena

From: Mikael [mailto:mikael-arons...@telia.com]
Sent: Wednesday, October 24, 2018 11:47 AM
To: user@ignite.apache.org
Subject: Re: OVER() clause in ignite


Hi!

As far as I know H2 does not support OVER.
Mikael
Den 2018-10-24 kl. 07:28, skrev Sriveena Mattaparthi:
Do we support over() clause in SQL in ignite like
select count(*) over() totalrecords  from EMPLOYEE;

please confirm.

Thanks & Regards,
Sriveena

"Confidentiality Notice: The contents of this email message and any attachments 
are intended solely for the addressee(s) and may contain confidential and/or 
privileged information and may be legally protected from disclosure. If you are 
not the intended recipient of this message or their agent, or if this message 
has been addressed to you in error, please immediately alert the sender by 
reply email and then delete this message and any attachments. If you are not 
the intended recipient, you are hereby notified that any use, dissemination, 
copying, or storage of this message or its attachments is strictly prohibited."

"Confidentiality Notice: The contents of this email message and any attachments 
are intended solely for the addressee(s) and may contain confidential and/or 
privileged information and may be legally protected from disclosure. If you are 
not the intended recipient of this message or their agent, or if this message 
has been addressed to you in error, please immediately alert the sender by 
reply email and then delete this message and any attachments. If you are not 
the intended recipient, you are hereby notified that any use, dissemination, 
copying, or storage of this message or its attachments is strictly prohibited."


Re: OVER() clause in ignite

2018-10-24 Thread Mikael

Hi!

As far as I know H2 does not support OVER.

Mikael

Den 2018-10-24 kl. 07:28, skrev Sriveena Mattaparthi:


Do we support over() clause in SQL in ignite like

select count(*) over() totalrecords  from EMPLOYEE;

please confirm.

Thanks & Regards,

Sriveena

“Confidentiality Notice: The contents of this email message and any 
attachments are intended solely for the addressee(s) and may contain 
confidential and/or privileged information and may be legally 
protected from disclosure. If you are not the intended recipient of 
this message or their agent, or if this message has been addressed to 
you in error, please immediately alert the sender by reply email and 
then delete this message and any attachments. If you are not the 
intended recipient, you are hereby notified that any use, 
dissemination, copying, or storage of this message or its attachments 
is strictly prohibited.”