Re: Service grid redesign

First, we must agree on names. I think the valuable word is 'deployment', though 'exchange' may be used too because there is an exchange of deployments maps during the deployment process. To avoid intersections with PME I suggest using the following names: ServicesFullMapMessage ->

Re: Service grid redesign

Hello, Vladimir. What is correct term? ср, 21 нояб. 2018 г., 10:29 Vladimir Ozerov voze...@gridgain.com: > Agree. Service deployment has nothing to do with PME. We should not use the > same term for different things. > > вт, 20 нояб. 2018 г. в 17:19, Denis Mekhanikov : > > > Vyacheslav, > > >

[GitHub] ignite pull request #5454: IGNITE-10356 JDBC thin driver returns wrong data ...

GitHub user ldzhjn opened a pull request: https://github.com/apache/ignite/pull/5454 IGNITE-10356 JDBC thin driver returns wrong data type for Date and Decimal SQL type You can merge this pull request into a Git repository by running: $ git pull

Re: Service grid redesign

Agree. Service deployment has nothing to do with PME. We should not use the same term for different things. вт, 20 нояб. 2018 г. в 17:19, Denis Mekhanikov : > Vyacheslav, > > I'm in process of reviewing your changes. Sorry for taking so long. > I posted the first portion of review comments

[jira] [Created] (IGNITE-10356) JDBC thin driver returns wrong data type for Date and Decimal SQL type

Ray created IGNITE-10356: Summary: JDBC thin driver returns wrong data type for Date and Decimal SQL type Key: IGNITE-10356 URL: https://issues.apache.org/jira/browse/IGNITE-10356 Project: Ignite

Ignite web console on kubernetes with ingress

Hi, I was trying to use Ignite web console on Kubernetes using the docker image at For external access, I am using ingress kubernetes resource. I am able to access Web console UI using the default href path (/). But with non default href path, the ignite web console page does not load. Is

[GitHub] ignite pull request #5453: IGNITE-10355 Tx rollback failure on put operation...

GitHub user x-kreator opened a pull request: https://github.com/apache/ignite/pull/5453 IGNITE-10355 Tx rollback failure on put operations with caches whose … …topology fails validation You can merge this pull request into a Git repository by running: $ git pull

Re: [ANNOUNCE] Welcome Igor Seliverstov as a new committer

Great news, Igor, hope to use this great feature in ML module! вт, 20 нояб. 2018 г. в 11:08, Павлухин Иван : > Igor my congratulations! Keep going! > > 2018-11-20 9:01 GMT+01:00, Vladimir Ozerov : > > The Apache Ignite Project Management Committee (PMC) has invited Igor > > Seliverstov to become

[jira] [Created] (IGNITE-10355) Tx rollback failure on put operations with caches whose topology fails validation.

Dmitriy Sorokin created IGNITE-10355: Summary: Tx rollback failure on put operations with caches whose topology fails validation. Key: IGNITE-10355 URL: https://issues.apache.org/jira/browse/IGNITE-10355

Re: [IMPORTANT] Future of Binary Objects

I'd like @Vyacheslav Daradur approach. Maybe somebody could have a look at UnsafeRow in Spark https://github.com/apache/spark/blob/master/sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/UnsafeRow.java UnsafeRow is a concrete InternalRow that represents a mutable internal

Re: New PMC Member: Nikolay Izhikov

Happy to hear! Good luck with the closest inegration with Spark! ср, 21 нояб. 2018 г. в 08:49, Vyacheslav Daradur : > Great news! Congrats Nikolay! > > вт, 20 нояб. 2018 г. в 23:22, Dmitriy Pavlov : > > > Hi Nikolay, > > > > please accept my congratulations! > > > > Sincerely, > > Dmitriy Pavlov

[MTCGA]: new failures in builds [2364043] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

Re: New PMC Member: Nikolay Izhikov

Great news! Congrats Nikolay! вт, 20 нояб. 2018 г. в 23:22, Dmitriy Pavlov : > Hi Nikolay, > > please accept my congratulations! > > Sincerely, > Dmitriy Pavlov > > вт, 20 нояб. 2018 г. в 22:54, Denis Magda : > > > The Project Management Committee (PMC) for Apache Ignite > > has invited Nikolay

[jira] [Created] (IGNITE-10354) Failing client node due to not receiving metrics updates

Roman Guseinov created IGNITE-10354: --- Summary: Failing client node due to not receiving metrics updates Key: IGNITE-10354 URL: https://issues.apache.org/jira/browse/IGNITE-10354 Project: Ignite

[MTCGA]: new failures in builds [2364039] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

[MTCGA]: new failures in builds [2364187] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

Re: proposed realization KILL QUERY command

Folks, The decimal syntax is really odd - KILL QUERY '[node_order].[query_counter]' Confusing, let's use a space to separate parameters. Also, what if I want to halt a specific query with certain ID? Don't know the node number, just know that the query is distributed and runs across several

Re: Request for Contributor Permissions

Hi Jonathan, I've added your account to the list of contributors, so you can now assign an issue to yourself. Welcome to the Apache Ignite Community! Sincerely, Dmitriy Pavlov вт, 20 нояб. 2018 г. в 23:53, Jonathan Camargo : > Hi, > > I would like to participate and to take the Jira

Re: [jira] [Created] (IGNITE-10353) Spring Add Update/Delete support for Spring Data

As a proposed design it will continue with the current way the lib is working, which is for the methods with the information about the query (i.e. findByIdOrderById() and in this case deleteByLastname()) it will create the query working over the PartTree, which is provided by the Spring framework,

Request for Contributor Permissions

Hi, I would like to participate and to take the Jira IGNITE-10353 Thanks -- Jonathan Giovanny Camargo Sanabria

[jira] [Created] (IGNITE-10353) Spring Add Update/Delete support for Spring Data

Jonathan Camargo created IGNITE-10353: - Summary: Spring Add Update/Delete support for Spring Data Key: IGNITE-10353 URL: https://issues.apache.org/jira/browse/IGNITE-10353 Project: Ignite

Re: New PMC Member: Nikolay Izhikov

Hi Nikolay, please accept my congratulations! Sincerely, Dmitriy Pavlov вт, 20 нояб. 2018 г. в 22:54, Denis Magda : > The Project Management Committee (PMC) for Apache Ignite > has invited Nikolay Izhikov to become a PMC member and we are pleased > to announce that he has accepted. > > Being a

Re: Time to remove automated messages from the devlist?

One more thing I want to emphasize here. We can't just remove messages, it _must_ be sent to some list, which is why we need some additional list, e.g. notifications@ for this. So only one option to proceed here is to run a formal vote on list creation and redirection of github/gitbox messages to

[GitHub] ignite pull request #5452: Ignite 2.4.12 p2

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/5452 Ignite 2.4.12 p2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.12-p2 Alternatively you can review and

New PMC Member: Nikolay Izhikov

The Project Management Committee (PMC) for Apache Ignite has invited Nikolay Izhikov to become a PMC member and we are pleased to announce that he has accepted. Being a PMC member enables assistance with the management and to guide the direction of the project. Please welcome Nikolay! Great

Re: TcpCommunicationSpi extension to ignore docker bridge network

What we prototyped was configuring via spring the list of IPs to ignore, because a given installation seemed to have a constant address for the bridge network, and this approach was reliable, once you know the bridge IPs. It is also a more general solution. When the container starts, you get a

Re: TcpCommunicationSpi extension to ignore docker bridge network

What we prototyped was configuring via spring the list of IPs to ignore, because a given installation seemed to have a constant address for the bridge network, and this approach was reliable, once you know the bridge IPs. When the container starts, you get a list of IP addresses from the kernel.

Re: Spring Update and delete queries

Excellent, Please get to know basics about Ignite's contribution process, create a ticket in JIRA and propose a design here. -- Denis On Tue, Nov 20, 2018 at 11:02 AM Jonathan Camargo wrote: > Hi, > > Sure, I'm ready to start working on the DELETE/UPDATE. > > El mar., 20 nov. 2018 a las

Re: TcpCommunicationSpi extension to ignore docker bridge network

Hi David, This is something we have also encountered recently and I was wondering how this can be mitigated in a general case. Do you know if an application can detect that it is being run in a docker container and add the corresponding list of bridge IPs automatically on start? If so, I this we

Re: Spring Update and delete queries

Hi, Sure, I'm ready to start working on the DELETE/UPDATE. El mar., 20 nov. 2018 a las 13:10, Denis Magda () escribió: > Hello Jonathan, > > Thanks for the feedback. Are you ready to work on missing DELETE/UPDATE > capabilities? Our community experts can guide you and do reviews. > > -- > Denis

Re: Spring Update and delete queries

Hello Jonathan, Thanks for the feedback. Are you ready to work on missing DELETE/UPDATE capabilities? Our community experts can guide you and do reviews. -- Denis On Tue, Nov 20, 2018 at 7:34 AM Jonathan Camargo wrote: > Hi community, > > First let me introduce myself, My name is Jonathan

[GitHub] ignite pull request #5451: IGNITE-10352 Fixed mapping of cache get request t...

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/5451 IGNITE-10352 Fixed mapping of cache get request to node while partition is in MOVING state …on is in MOVING state You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #5046: IGNITE-9959: Set consistent id in tests

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5046 ---

[jira] [Created] (IGNITE-10352) Cache get request can be mapped to node while partition in MOVING state

Andrey Gura created IGNITE-10352: Summary: Cache get request can be mapped to node while partition in MOVING state Key: IGNITE-10352 URL: https://issues.apache.org/jira/browse/IGNITE-10352 Project:

[GitHub] ignite pull request #5450: IGNITE-10298 Cover possible deadlock in case of c...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/5450 IGNITE-10298 Cover possible deadlock in case of caches start and frequent checkpoints You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-10351) Web Console: add new fields of IgniteConfiguration (sysWorkerBlockedTimeout and checkpointReadLockTimeout) to UI configurator

Alexey Kuznetsov created IGNITE-10351: - Summary: Web Console: add new fields of IgniteConfiguration (sysWorkerBlockedTimeout and checkpointReadLockTimeout) to UI configurator Key: IGNITE-10351 URL:

JdbcColumnMeta

Dear Devs,    I would like to help expand the jdbc resultset metadata available when querying a table. Consider the following example: CREATE TABLE ARTICLE (     ID BIGINT,     BODY text,     LAST_MODIFIED TIMESTAMP with time zone,     CONSTRAINT PK_ ARTICLE PRIMARY KEY (ID) ); After

[jira] [Created] (IGNITE-10350) Document that now it's allowed to stop caches created via SQL/DDL

Eduard Shangareev created IGNITE-10350: -- Summary: Document that now it's allowed to stop caches created via SQL/DDL Key: IGNITE-10350 URL: https://issues.apache.org/jira/browse/IGNITE-10350

TcpCommunicationSpi extension to ignore docker bridge network

We see some annoying behavior with S3 discovery because Ignite will push to the discovery S3 bucket the IP address of the local docker bridge network (172.17.0.1) in our case. Basically, each node when coming online tries that address first, and has to go through a network timeout to recover.

[jira] [Created] (IGNITE-10349) Web Console: Add check for supported MongoDb version before WC start

Alexey Kuznetsov created IGNITE-10349: - Summary: Web Console: Add check for supported MongoDb version before WC start Key: IGNITE-10349 URL: https://issues.apache.org/jira/browse/IGNITE-10349

[jira] [Created] (IGNITE-10348) Safely recreate metastore to mitigate IGNITE-8735

Alexey Goncharuk created IGNITE-10348: - Summary: Safely recreate metastore to mitigate IGNITE-8735 Key: IGNITE-10348 URL: https://issues.apache.org/jira/browse/IGNITE-10348 Project: Ignite

[GitHub] ignite pull request #5435: temporary PR to verify renamed tests on Teamcity ...

Github user oignatenko closed the pull request at: https://github.com/apache/ignite/pull/5435 ---

Spring Update and delete queries

Hi community, First let me introduce myself, My name is Jonathan Camargo, I'm a Java developer at a software outsourcing company, I'm currently working for a legacy project. I'm currently learning new technologies and concepts such as IMDG, I have been reading concepts and code about that mainly

[jira] [Created] (IGNITE-10347) Expose system SQL view for running queries

Yury Gerzhedovich created IGNITE-10347: -- Summary: Expose system SQL view for running queries Key: IGNITE-10347 URL: https://issues.apache.org/jira/browse/IGNITE-10347 Project: Ignite

Re: Service grid redesign

Denis, thanks for your participation! >> There is no exchange in case of service deployment There is some kind of exchange of services map which describes mapping services instances to nodes in the cluster. I'm a bit confused because of your notes about naming, the main goal was to do the code

[GitHub] ignite pull request #5449: Tests for ignite 10343

GitHub user 1vanan opened a pull request: https://github.com/apache/ignite/pull/5449 Tests for ignite 10343 You can merge this pull request into a Git repository by running: $ git pull https://github.com/1vanan/ignite tests-IGNITE-10343 Alternatively you can review and apply

[jira] [Created] (IGNITE-10346) Improve TcpDiscoveryVmIpFinder usability in Yardstick

Oleg Ostanin created IGNITE-10346: - Summary: Improve TcpDiscoveryVmIpFinder usability in Yardstick Key: IGNITE-10346 URL: https://issues.apache.org/jira/browse/IGNITE-10346 Project: Ignite

[GitHub] asfgit closed pull request #75: IGNITE-10319 Suite compilation error failure handling added

asfgit closed pull request #75: IGNITE-10319 Suite compilation error failure handling added URL: https://github.com/apache/ignite-teamcity-bot/pull/75 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of

Re: Service grid redesign

Vyacheslav, I'm in process of reviewing your changes. Sorry for taking so long. I posted the first portion of review comments yesterday. I'd like to finish looking through the code. I'll post more comments later. I see, that you called things analogously to partition map exchange. I realize,

[GitHub] ignite pull request #5436: IGNITE-10043 Do not reset LOST partitions when on...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5436 ---

[GitHub] ignite pull request #5448: IGNITE-10277 set prepared state before send prepa...

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/5448 IGNITE-10277 set prepared state before send prepare message You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #5447: IGNITE-10343

GitHub user 1vanan opened a pull request: https://github.com/apache/ignite/pull/5447 IGNITE-10343 You can merge this pull request into a Git repository by running: $ git pull https://github.com/1vanan/ignite IGNITE-10343 Alternatively you can review and apply these changes

[jira] [Created] (IGNITE-10345) Discontinue forceServerMode support for client nodes.

Andrew Mashenkov created IGNITE-10345: - Summary: Discontinue forceServerMode support for client nodes. Key: IGNITE-10345 URL: https://issues.apache.org/jira/browse/IGNITE-10345 Project: Ignite

[GitHub] ignite pull request #5446: IGNITE-10193: IgniteBaselineAffinityTopologyActiv...

GitHub user avplatonov opened a pull request: https://github.com/apache/ignite/pull/5446 IGNITE-10193: IgniteBaselineAffinityTopologyActivationTest#testBaselineTopologyHistoryIsDeletedOnBaselineDelete fails You can merge this pull request into a Git repository by running: $

[jira] [Created] (IGNITE-10344) Speed up cleanupRestoredCaches

Pavel Voronkin created IGNITE-10344: --- Summary: Speed up cleanupRestoredCaches Key: IGNITE-10344 URL: https://issues.apache.org/jira/browse/IGNITE-10344 Project: Ignite Issue Type:

[GitHub] ignite pull request #5371: IGNITE-9999 Logical recovery cleanup and refactor...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5371 ---

[GitHub] ignite pull request #5189: IGNITE-9828: Continuous query failover.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5189 ---

[GitHub] ignite pull request #5444: IGNITE-10341 Added lost policy tests with persist...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5444 ---

[GitHub] SomeFire commented on a change in pull request #76: IGNITE-10275 Refactor of visa caching.

SomeFire commented on a change in pull request #76: IGNITE-10275 Refactor of visa caching. URL: https://github.com/apache/ignite-teamcity-bot/pull/76#discussion_r234972281 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/ObserverTask.java ##

[GitHub] ignite pull request #5407: Ignite-10217

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5407 ---

[jira] [Created] (IGNITE-10342) TC: Create "Run :: MVCC" suite.

Andrew Mashenkov created IGNITE-10342: - Summary: TC: Create "Run :: MVCC" suite. Key: IGNITE-10342 URL: https://issues.apache.org/jira/browse/IGNITE-10342 Project: Ignite Issue Type:

[GitHub] ignite pull request #5431: IGNITE-10328

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5431 ---

[GitHub] ignite pull request #5445: IGNITE-10236: MVCC: Create "Cache 3" test suite f...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/5445 IGNITE-10236: MVCC: Create "Cache 3" test suite for MVCC mode. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Code inspection

Hello, Vyacheslav. Yes, we have. Maxim Muzafarov, can you fix it, please? вт, 20 нояб. 2018 г., 13:10 Vyacheslav Daradur daradu...@gmail.com: > Guys, why we have 2 different inspection files in the repo? > idea\ignite_inspections.xml > idea\ignite_inspections_teamcity.xml > > AFAIK TeamCity is

[GitHub] ignite pull request #5444: IGNITE-10341 Added lost policy tests with persist...

GitHub user dgovorukhin opened a pull request: https://github.com/apache/ignite/pull/5444 IGNITE-10341 Added lost policy tests with persistence enable You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #5443: IGNITE-10318 Web console: use newer panels in que...

GitHub user Klaster1 opened a pull request: https://github.com/apache/ignite/pull/5443 IGNITE-10318 Web console: use newer panels in query notebook screen [The issue](https://issues.apache.org/jira/browse/IGNITE-10318). You can merge this pull request into a Git repository by

[jira] [Created] (IGNITE-10341) Missed loss policy tests with persistence

Dmitriy Govorukhin created IGNITE-10341: --- Summary: Missed loss policy tests with persistence Key: IGNITE-10341 URL: https://issues.apache.org/jira/browse/IGNITE-10341 Project: Ignite

[GitHub] ignite pull request #5442: IGNITE-8913

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/5442 IGNITE-8913 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8913-1 Alternatively you can review and apply

[GitHub] ignite pull request #5441: IGNITE-5439 Jdbc thin cancel implemented.

GitHub user sanpwc opened a pull request: https://github.com/apache/ignite/pull/5441 IGNITE-5439 Jdbc thin cancel implemented. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5439 Alternatively you

Re: Code inspection

Guys, why we have 2 different inspection files in the repo? idea\ignite_inspections.xml idea\ignite_inspections_teamcity.xml AFAIK TeamCity is able to use the same inspection file with IDE. I've imported 'idea\ignite_inspections.xml' in the IDE, but now see inspection warnings for my PR on TC

[jira] [Created] (IGNITE-10340) JDBC thin: in some cases it's not possible to convert IllegalStateException to SQLException with appropriate message.

Alexander Lapin created IGNITE-10340: Summary: JDBC thin: in some cases it's not possible to convert IllegalStateException to SQLException with appropriate message. Key: IGNITE-10340 URL:

Re: Apache Ignite 2.7. Last Mile

Yes, revert both. вт, 20 нояб. 2018 г., 11:52 Vladimir Ozerov voze...@gridgain.com: > +1 for reverting both. > > On Tue, Nov 20, 2018 at 9:43 AM Nikolay Izhikov > wrote: > > > Hello, Dmitrii. > > > > I see 2 tickets for this improvement: > > > > IGNITE-602 - [Test] GridToStringBuilder is

[GitHub] ignite pull request #5421: IGNITE-8765: Fixed event's query type

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5421 ---

[GitHub] ignite pull request #5336: IGNITE-10159: IgniteCacheAbstractQuerySelfTest.te...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5336 ---

[GitHub] ignite pull request #5362: IGNITE-9996: comment out pageSize for encmgr

Github user nizhikov closed the pull request at: https://github.com/apache/ignite/pull/5362 ---

Re: Service grid redesign

Denis, Yakov have you had a chance to review the solution? Igniters, we need to define a list of reviewers, otherwise no end in sign. I'm ready to continue work on the Service Grid, including new features like hot-redeployment and versioning, also, I have ideas about new tools for monitoring and

Re: proposed realization KILL QUERY command

Hi Vladimir, Thanks for your suggestion to use MANAGEMENT_POOL for processing cancellation requests. About your questions. 1) I'm going to implements SQL view to provide list of running queries. The SQL VIEW has been a little bit discussed earlier. Proposed name is *running_queries* with

[jira] [Created] (IGNITE-10339) Connection to cluster failed in control.sh while using --cache

Ivan Daschinskiy created IGNITE-10339: - Summary: Connection to cluster failed in control.sh while using --cache Key: IGNITE-10339 URL: https://issues.apache.org/jira/browse/IGNITE-10339 Project:

Re: Apache Ignite 2.7. Last Mile

+1 for reverting both. On Tue, Nov 20, 2018 at 9:43 AM Nikolay Izhikov wrote: > Hello, Dmitrii. > > I see 2 tickets for this improvement: > > IGNITE-602 - [Test] GridToStringBuilder is vulnerable for > StackOverflowError caused by infinite recursion [1] > IGNITE-9209 -

[GitHub] ololo3000 opened a new pull request #76: IGNITE-10275 Refactor of visa caching,

ololo3000 opened a new pull request #76: IGNITE-10275 Refactor of visa caching, URL: https://github.com/apache/ignite-teamcity-bot/pull/76 This is an automated message from the Apache Git Service. To respond to the message,

Re: [IMPORTANT] Future of Binary Objects

I really like Protobuf format. It is probably not what we need for O(1) fields access, but for compact data representation we can derive lots from there. Also IMO, restricting field type change is absolutely sane idea. The correct way to evolve schema in common case is to add new fields and

[GitHub] ignite pull request #5347: IGNITE-10162: IgniteCacheAtomicQuerySelfTest#test...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5347 ---

Re: [IMPORTANT] Future of Binary Objects

I think, one of a possible way to reduce overhead and TCO - SQL Scheme approach. That assumes that metadata will be stored separately from serialized data to reduce size. In this case, the most advantages of Binary Objects like access in O(1) and access without deserialization may be achieved. On

Re: [ANNOUNCE] Welcome Igor Seliverstov as a new committer

Igor my congratulations! Keep going! 2018-11-20 9:01 GMT+01:00, Vladimir Ozerov : > The Apache Ignite Project Management Committee (PMC) has invited Igor > Seliverstov to become a new committer and are happy to announce that he has > accepted. > > Igor contributed a lot to "Transactional SQL"

[ANNOUNCE] Welcome Igor Seliverstov as a new committer

The Apache Ignite Project Management Committee (PMC) has invited Igor Seliverstov to become a new committer and are happy to announce that he has accepted. Igor contributed a lot to "Transactional SQL" feature. Please join me in welcoming Igor and congratulating him on his new role in the Apache