NTILE function (ignite)

IS NTILE function is possible in ignite database -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Cannot connect the ignite server after running one or two days

Hi, We have deployed ignite 2.3 and created about 100 caches and load data from oracle into these caches. But clients(started in developing tomcat web apps, we often start and stop these apps) often cannot connect the ignite server after one or two days. By searching logs, we found below

Re: Questions about SQL interface

Hello Slava, the workaround totally works for me, I already have an Interceptor for certain caches anyway. Thanks a lot for looking into this. Will you take care of the jira ticket, too? Cheers Wolfram On 23/01/2018 06:19, slava.koptilin wrote: Hello, Here is the SQL statement and the

RE: Creating multiple Ignite grids on same machine

Hi Alexey, Works like a charm!  Thanks, Raymond. -Original Message- From: Alexey Popov [mailto:tank2.a...@gmail.com] Sent: Wednesday, January 10, 2018 9:03 PM To: user@ignite.apache.org Subject: Re: Creating multiple Ignite grids on same machine Hi Raymond, In your case you should

Re:Re:Re: Re:Re: delete data error

Sorry, the fid is not UUID in tmpCompanyCuBaseDataCache , but the other are UUID. The error is not happened only in this cache, the other are the same. I found when I delete a single record ,it's nomal .But If I delete many records in a SQL,it will get the wrong. Thanks. At 2018-01-23

Re:Re: Re:Re: delete data error

I put the entry like this: cache.put(entry.getFID(),entry); The fid is a UUID, is only. I'm very sure that the data in the cache is no problem. All value is correct,and look like the other record. sql="delete from \"tmpCompanyCuBaseDataCache\".TmpCompanyCuBaseData where

Key Value Store - control TTL refresh

I'd like to set TTL for all entries in some map. Along with that I'd like to control operations that refresh TTL. For instance simple Read/Write should update the TTL, but pulling the whole map should not. Is that something that can be done with current expiry policies?

Ignite 2.x upgrade guidelines

Hi, we are upgrading ignite 1.7.0 to 2.3.0 soon. on 1.7 we were on heap and used G1GC with 16 nodes each using 30 GB heap. Although we never ended up using more than 40% heaps on any node at a given time. With 2.3.0 it would be all off-heap. Are there any guidelines to follow or things to check

Re: Questions about SQL interface

Hello, > Here is the SQL statement and the exception from the logs: > https://gist.github.com/wolframite/d0b28d8b7ce483f82b9fd145adb68abe I tried this use-case with cache configuration you provided and I was able to reproduce the issue. When insert/update operation is executed via SQL api, the

Re: Long activation times with Ignite persistence enabled

Alexey, Thanks a lot for looking into this! My configuration is very basic: 3 caches all using standard 1024 partitions, sharing a 1GB persistent memory region. Please find below the stack trace of the exchange worker thread captured while the node's activation is in progress (2.4 Ignite

Question about persisting stream processing results

Hi! I'm receiving two streams of events, stream one (1) is basically only used as basis for interpolating and putting data in stream two (2). Whenever an element in stream (1) arrives, the local listener of my ContinuousQuery starting searching the previous element belonging to the same group.

Re: query on BinaryObject index and table

The schema can be changed with ALTER TABLE ADD COLUMN command: https://apacheignite-sql.readme.io/docs/alter-table To my knowledge this is supported for schemas that were initially configured by both DDL and QueryEntity/Annotations. — Denis

Re: CacheWriterException: Failed to write entry to database

Hello. It seems that your Oracle data source is not configured properly: Caused by: java.sql.SQLException: Invalid Oracle URL specified: OracleDataSource.makeURL Unfortunately you did not include that part of source so I can't say anything more. Regards, -- Sent from:

Re: Re:Re: delete data error

Hello! Thank you for the log! It looks like there's some internal consistency problem with the cache. >From the log content the root cause is not apparent. Can you please try getting the offending key from cache via Cache API (see if it's everything all right with it), and then deleting the key

Re: query on BinaryObject index and table

Hello Rajesh! Table name can be specified in cache configuration's query entity. If not supplied, by default it is equal to value type name, e.g. BinaryObject :) Also, note that SQL tables have fixed schemas. This means you won't be able to add a random set of fields in BinaryObject and be able

Re: CacheStoreAdapter write and delete are not being called by Ignite's GridCacheStoreManager

Hi Pim, Well, you only configure CacheLoaderFactory which is used when a cache is read-through or when loading data into a cache via the Cache#loadAll() method. So, you need to provide a CacheWriter implementation in order to enable write-through behavior. Please see,

Re: DataStreamer does not persist in cache when a receiver is set

Hi, Please share a full code of your EntryProcessor. Which logger do you use here? Thanks, Evgenii 2018-01-20 21:00 GMT+03:00 Pim D : > Hi, > > I have created a datastreamer that will stream data from a database to my > cache. > This works very nice, untill... > ... I

Re: .Net standard target for Ignite.Net client

2.4 is expected in a couple of weeks: http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-4-release-td26031.html On Mon, Jan 22, 2018 at 1:12 PM, Raymond Wilson wrote: > Hi Pavel, > > That is very good news! :) > > When do you expect 2.4 to be

Re: .Net standard target for Ignite.Net client

Hi Pavel, That is very good news! :) When do you expect 2.4 to be released Thanks, Raymond. Sent from my iPhone > On 22/01/2018, at 9:22 PM, Pavel Tupitsyn wrote > > Hi Raymond, > > Upcoming Ignite 2.4 has a lot of changes to run Ignite.NET under .NET Core on >

Re: Long activation times with Ignite persistence enabled

Andrey, Can you please describe in greater detail the configuration of your nodes (specifically, number of caches and number of partitions). Ignite would not load all the partitions into memory on startup simply because there is no such logic. What it does, however, is loading meta pages for each

Re: .Net standard target for Ignite.Net client

Hi Raymond, Upcoming Ignite 2.4 has a lot of changes to run Ignite.NET under .NET Core on Linux and macOS (as well as Windows). However, we are not targeting .NET Standard, since it misses some crucial things like DynamicMethod. Please make sure that you don't confuse .NET Standard and .NET