Workaround for possible NPE in Selector.open()

Hi Igniters, Today I noticed quite old code aimed to workaround an old bug in 1.5 JDK revision which was fixed in rev 1.7 org/apache/ignite/internal/util/nio/GridNioServer.java:161 Since we widely use lambdas now (so Ignite requires at least Java 1.8) do we really need it now? I would like to

Re: Mark MVCC with @IgniteExperimental

Note that someone uses it Main problem is a recovery process when persistence enabled and a cluster have more than one node. It is a problem even for regular transactional caches, the main difference - MVCC detects any inconsistencies while regular transactional caches may ignore it without a

Re: [IGNITE-12582] Configuration by property

Isn't a better way just to add a new annotation? Like RepositoryConfig but from v2 package for example. This case whose who already use it won't suffer. Also it's would be great to provide a way to escape constants which are similar to spel expressions. Regards, Igor чт, 30 янв. 2020 г., 13:18

New SQL engine, review/feedback request

Hi guys, Some of you know, I'm working on a brand new Calcite based SQL engine. So, now I have some intermediate results and need a feedback from community. A feature branch with a concept of a module is ignite-12248 . The module is going to b

Re: SQL dialects supported by Calcite

Forgot to mention, it's better to set chosen dialect per session, for example by a command "alter session sed dialect=ORACLE" Or a part of connection url. Global configuration parameter isn't a good choice. сб, 28 дек. 2019 г., 11:02 Seliverstov Igor : > I guess

Re: SQL dialects supported by Calcite

> - > Denis > > > On Fri, Dec 27, 2019 at 7:05 AM Seliverstov Igor > wrote: > > > Denis, > > > > > Is it true that Calcite can parse MySQL, Oracle > > > > Yes, it can. > > > > > Do I need to select a dialect globally or can it be set o

Re: SQL dialects supported by Calcite

Denis, > Is it true that Calcite can parse MySQL, Oracle Yes, it can. > Do I need to select a dialect globally or can it be set on a per-query > level? Technically a parser, a validator, a planner, other components are created and configured for each query call (because they are stateful). So

Re: Adding support for Ignite secondary indexes to Apache Calcite planner

Colleagues, As far as I understand, materialization acts like a special rule, that matches some subtree pattern (a leaf part of a query plan) to a star table, which may have better cost than the subtree, it replaces. Saying that, in general, there is no difference between approaches - they do t

Calcite based SQL query engine. Local queries

Hi Igniters, Working on new generation of Ignite SQL I faced a question: «Do we need local queries at all and, if so, what semantic they should have?». Current planing flow consists of next steps: 1) Parsing SQL to AST 2) Validating AST (against Schema) 3) Optimizing (Building execution graph)

Re: Ignite community is building Calcite-based prototype

Guys, The better link: https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine Almost everything you may see by the link is the same as Drill guys already did, the differenc

Re: New SQL execution engine

Nikolay, The document you edited is wrong (and outdated). Since the author meant another idea, I decided not to change IEP-35 and create a new one - IEP-37 (https://cwiki.apache.org/confluence/x/NBLABw). It's already have a number of key requirements. Regards, Igor вт, 1 окт. 2019 г., 6:14 Niko

Re: New SQL execution engine

QL > engine for several releases. > > Ignite has too many partially implemented features to include on more :) > > Let's start with the IEP clarification and replace the SQL engine with the > best one for Ignite good. > > > В Пт, 27/09/2019 в 18:08 +0300, Se

Re: New SQL execution engine

me - replacement of SQL engine to some more customizable make > sense for me. > But, this kind of decisions need carefull discussion. > > В Пт, 27/09/2019 в 17:08 +0300, Seliverstov Igor пишет: >> Nikolay, >> >> The main issue - there is no *selection*. >> >&g

Re: New SQL execution engine

Nikolay, The main issue - there is no *selection*. There is a field of knowledge - relational algebra, which describes how to transform relational expressions saving their semantics, and a couple of implementations (Calcite is only one written in Java). There are only two alternatives: 1) Imp

Re: [DISCUSSION][IEP-35] Metrics configuration

Igniters, One more question on topic. Should we preserve metrics configuration on restart? (I think we should) If so, which configuration use after restart? Defined in config file or saved in config storage? (I guess, saved configuration should have a priority) So, how to tell users that any c

Re: Suggestion to improve deadlock detection

uot;. Today we have 2PL and there is no activity on > > implementing rollback to savepoint. And if we do it in the future we > > will have to return to the subject of deadlock detection anyway. > > > > I will proceed with "forward-only" approach. > >

Re: Suggestion to improve deadlock detection

Ivan, I would prefer forward-only implementation even knowing it allows false positive check results. Why I think so: 1) From my experience, when we have any future is waiting for reply, we have to take a failover into consideration. Usually failover implementations are way more complex than an

Re: Page eviction for in-memory mode with enabled MVCC

Roman, I would prefer first option. The fact user uses MVCC says he needs some more strict guaranties which cannot meet in other modes. I would rollback both txs in case we cannot provide such guaranties. Regards, Igor пт, 14 дек. 2018 г. в 15:36, Roman Kondakov : > Vladimir, > > I was thinkin

Re: Apache Ignite 2.7. Last Mile

e/commit/51a202a4c48220fa919f47147bd4889033cd35a8 > > > > > was commited on the 15 October. I could not take a look on the > > testAtomicOnheapTwoBackupAsyncFullSync before this date, because the > oldest > > test in the history on TC dates 12 November. > &g

Re: [VOTE] Apache Ignite 2.7.0 RC1

+1 пт, 30 нояб. 2018 г., 9:59 Nikolay Izhikov nizhi...@apache.org: > Igniters, > > We've uploaded a 2.7.0 release candidate to > > https://dist.apache.org/repos/dist/dev/ignite/2.7.0-rc1/ > > Git tag name is 2.7.0-rc1 > > This release includes the following changes: > > Apache Ignite In-Memory Da

Re: Historical rebalance

one operation ahead *each other > > 2) Demander goes to the past and finds update counter which was current > at > > the time of last TX completed operation > > 3) Supplier goes to the closest checkpoint in the past where this update > > counter either doesn't exist or

Re: Apache Ignite 2.7. Last Mile

Ivan, Could you provide a bit more details? I don't see any NPE among all available logs. I don't think the issue is caused by changes in scope of IGNITE-7953. The test fails both before

Re: Historical rebalance

Иван : > > > > > > Hi, > > > > > > Regarding Vladimir's new idea. > > > > We assume that transaction can be represented as a set of > independent operations, which are applied in the same order on both primary > and backup nodes. >

Re: [VOTE] Creation dedicated list for github notifiacations

+1 вт, 27 нояб. 2018 г. в 14:45, Юрий : > +1 > > вт, 27 нояб. 2018 г. в 11:22, Andrey Mashenkov >: > > > +1 > > > > On Tue, Nov 27, 2018 at 10:12 AM Sergey Chugunov < > > sergey.chugu...@gmail.com> > > wrote: > > > > > +1 > > > > > > Plus this dedicated list should be properly documented in wiki

Re: Historical rebalance

ear the candidate list and remove an associated tx from the active list if present. Use back-counter instead of actual update counter in demand message. вт, 27 нояб. 2018 г. в 12:56, Seliverstov Igor : > Ivan, > > 1) The list is saved on each checkpoint, wholly (all transactions in >

Re: Historical rebalance

message: "Give me all updates starting > from that LWM plus data for that transactions which were active when I > failed". > > Am I right? > > On Fri, Nov 23, 2018 at 11:22 AM Seliverstov Igor > wrote: > > > Hi Igniters, > > > > Currently I’m wo

Historical rebalance

Hi Igniters, Currently I’m working on possible approaches how to implement historical rebalance (delta rebalance using WAL iterator) over MVCC caches. The main difficulty is that MVCC writes changes on tx active phase while partition update version, aka update counter, is being applied on tx fi

Re: MVCC and IgniteDataStreamer

Ivan, Anyway DataStreamer is the fastest way to deliver data to a data node, the question is how to apply it correctly. I don’t thing we need one more tool, which 90% is the same as DataStreamer. All we need is just to implement a couple of new stream receivers. Regards, Igor > 13 июля 2018 г

Re: MVCC and IgniteDataStreamer

Yakov, We can introduce several modes: 1) initial loading which replaces data (allowOverwrite=true) with initial version or leaves it as is (allowOverwrite=false) and requires exclusive table lock (fastest one) 2) continuous loading which has its own version and links the data as regular trans

MVCC and IgniteDataStreamer

Hi Igniters, You know, we're currently developing fair MVCC for transactional caches ( https://issues-test.apache.org/jira/plugins/servlet/mobile#issue/IGNITE-4191 ). At now we're trying to make work IgniteDataStreamer with MVCC. The problem is that MVCC requires linking between versions for che

Re: [DISCUSSION] Urgent Ignite bug fix release

e thresholds? > > On Mon, Aug 28, 2017 at 4:56 AM, Seliverstov Igor > wrote: > > > The suggestion here is based on initial settings, and it's so because > there > > is no other nodes on the host in the example. > > > > The algorithm tries to preserve the o

Re: [DISCUSSION] Urgent Ignite bug fix release

th 8GB will completely exhaust the available memory. I would suggest 6 or > 7GB. > > Also, why 100MB for default policy. Anything under 1GB seems too small. > > Can you please comment? > > D. > > On Mon, Aug 28, 2017 at 3:31 AM, Seliverstov Igor > wrote: &

Re: [DISCUSSION] Urgent Ignite bug fix release

e overall memory usage by all Ignite nodes on the host: value > >> --- > >> > >> Records in […] are optional. If custom memory policy is not set or the > >> default memory policy is overridden the output will miss some of the &

Re: [DISCUSSION] Urgent Ignite bug fix release

r, what is this flood of WARN messaging coming after the text? Are we > really going to print this whole thing out? > > On Fri, Aug 25, 2017 at 9:49 AM, Seliverstov Igor > wrote: > > > This message appears on topology change in case the available memory is > > exceeded

Re: [DISCUSSION] Urgent Ignite bug fix release

This message appears on topology change in case the available memory is exceeded 2017-08-25 19:47 GMT+03:00 Seliverstov Igor : > An example of current impl: > > > [2017-08-25 19:44:37,740][WARN ][disco-event-worker-#29%internal. > GridHomePathSelfTest0%][GridDiscoveryManager] >

Re: [DISCUSSION] Urgent Ignite bug fix release

mory allocated > for > > > each node. > > > > > > Also, can we calculate what the memory size allocated for each node > should > > be? In that case we should suggest it. > > > > D. > > > > > > On Fri, Aug 25, 2017 at 7:20 AM, Se

Re: [DISCUSSION] Urgent Ignite bug fix release

What do you, guys think about next warning? [2017-08-25 17:17:04,718][INFO ][test-runner-#1%internal.GridHomePathSelfTest%][GridHomePathSelfTest0] System cache's MemoryPolicy size is configured to 40 MB. Use MemoryConfiguration.systemCacheMemorySize property to change the setting. [2017-08-25 17:1

ignite-pds and binary objects

Hi guys! Seems the new persistance feature is not compatable with our default configuration. A simplest test where I store an object type, restart the grid and try to get the object by its key fails with NPE: java.lang.NullPointerException at org.apache.ignite.internal.processors.cache.binar

Re: Null cache names

r each data type. > > > Roman > > > > > > > > >On Monday, April 24, 2017 12:15 AM, Denis Magda < > dma...@gridgain.com > > > > > > wrote: > > > > > > > > > Roman, would you suggest a quick solution for th

Re: Null cache names

; > >On Monday, April 24, 2017 12:15 AM, Denis Magda < > dma...@gridgain.com > > > > > > wrote: > > > > > > > > > Roman, would you suggest a quick solution for the redis integration or > > > even > > > implement it in the nearest

Re: Null cache names

s integration should > work as is (I have to recheck it, what is the JIRA ticket for the null > cache issue?) > Do you just want to be sure your changes don't affect the Redis > integration, or do you want to extend it to switch between caches? > Roman > > On Friday, Ap

Null cache names

Hi Roman, As far as I inderstand you're the author of the Redis protocol implementation. Currently I'm working on a task to prohibit null names for caches and I've found that current implementation implies using of default (aka null named) cache as a Redis database. So, I need your assistance to

Re: [VOTE] Apache Ignite 1.9.0 RC2

+1 2 мар. 2017 г. 11:45 ПП пользователь "Valentin Kulichenko" < valentin.kuliche...@gmail.com> написал: > +1 (binding) > > -Val > > On Thu, Mar 2, 2017 at 11:33 AM, Denis Magda wrote: > > > +1 (binding) > > > > — > > Denis > > > > > On Mar 2, 2017, at 9:02 AM, Anton Vinogradov > > > wrote: > >

JIRA ticket

Hi guys! Doesn't anybody mind if I take IGNITE-4681 ticket? Regards, Igor

Hello

Hello everyone! My name is Igor, I'm a novice in this community but wish to put my efforts into the project) Could anybody describe me how to join the Ignate project on Apache Ignite JIRA ? Thanks in advance Igor