[GitHub] ignite pull request #1267: IGNITE-4284 - Test

Github user dkarachentsev closed the pull request at: https://github.com/apache/ignite/pull/1267 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

Re: IGNITE-4188, savepoints with atomic cache?

As far as I know operations on atomic caches are applied immediately dishonoring any tx context. I would suggest that atomic cache update operation called from active tx throws illegal state exception, unless user intentionally permits this update by calling atomicCache.withAllowInTx() (similar

[GitHub] ignite pull request #1682: IGNITE-3939 Compact long zero values binary repre...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1682 IGNITE-3939 Compact long zero values binary representation You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: IgniteMessaging in async mode

Dmitry, When you work with distributed system you cannot ignore the fact that it is distributed. Agree with Valya that we do not need to do anything here, user should handle this case on his own. On Tue, Mar 28, 2017 at 2:35 PM, Dmitry Karachentsev < dkarachent...@gridgain.com> wrote: > I'm

Please review IGNITE-4838

Igniters, https://issues.apache.org/jira/browse/IGNITE-4838 http://reviews.ignite.apache.org/ignite/review/IGNT-CR-136 Yakov, as most expert in Compute Grid, could you take a look? -- Alexey Kuznetsov

[GitHub] ignite pull request #1684: IGNITE-4575: fix javadoc

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1684 IGNITE-4575: fix javadoc You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4575-javadoc Alternatively

Re: IgniteMessaging in async mode

I'm talking about real case [1]. User actually doesn't care about difficulties of connection establishing or if message wasn't sent. But now he has to manually resolve such case. Why not to use existing async mode here? -Dmitry. [1]

IGNITE-4188, savepoints with atomic cache?

Hello, community. How should savepoint and rollback to savepoint react to the atomic caches inside transaction? I think they should ignore such entries, but I want to know opinion of more competent igniters. https://issues.apache.org/jira/browse/IGNITE-4188

[jira] [Created] (IGNITE-4874) SQL engine should throw meaningful exception on query from local cache

Vasiliy Sisko created IGNITE-4874: - Summary: SQL engine should throw meaningful exception on query from local cache Key: IGNITE-4874 URL: https://issues.apache.org/jira/browse/IGNITE-4874 Project:

[GitHub] ignite pull request #1683: IGNITE-4577: fix javadoc

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1683 IGNITE-4577: fix javadoc You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-fix-cache-javadoc

[GitHub] ignite pull request #1683: IGNITE-4575: fix javadoc

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1683 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

Re: Please review IGNITE-4838

Alex, I will try to review this in a couple of days. --Yakov

[jira] [Created] (IGNITE-4872) GridQueryIndexing.registerType should return void

Vladimir Ozerov created IGNITE-4872: --- Summary: GridQueryIndexing.registerType should return void Key: IGNITE-4872 URL: https://issues.apache.org/jira/browse/IGNITE-4872 Project: Ignite

Re: Continuations for services

Valya, Could you please point me where we delegate thread to another pool? I remember we did something around this when working with some streamer problems. On Tue, Mar 28, 2017 at 4:18 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Vova, > > Agree, I already merged

[GitHub] ignite pull request #1680: IGNITE-3487: Made _key and _val columns hidden

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/1680 IGNITE-3487: Made _key and _val columns hidden You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3487

[jira] [Created] (IGNITE-4873) Web console: Improve log when agent try to connect to not Ignite node.

Vasiliy Sisko created IGNITE-4873: - Summary: Web console: Improve log when agent try to connect to not Ignite node. Key: IGNITE-4873 URL: https://issues.apache.org/jira/browse/IGNITE-4873 Project:

[GitHub] ignite pull request #1684: IGNITE-4575: fix javadoc

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1684 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1686: IGNITE-4669 .NET: Sort binary object fields

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1686 IGNITE-4669 .NET: Sort binary object fields You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4669

Re: Logging ignite-log4j.jar

IGNITE-4863 [1] is ready for review. Fix prevents RootLogger (log4j-1.x) log level from being changed if it can have negative affect other loggers. [1] https://issues.apache.org/jira/browse/IGNITE-4863

Re: IGNITE-4284 - ready for review

Hi Nikita, I've looked through the issue and, because fix is quite small and important, committed to PR#1681 [1]. Please take a look at it. Here is the code review [2]. I'll assign it to myself and resolve. If you have any questions about fix, please ask. Thanks for your effort! [1]

[GitHub] ignite pull request #1685: Ignite 4868

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

[GitHub] ignite pull request #1687: IGNITE-4863: Log4jLogger can change RootLogger lo...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1687 IGNITE-4863: Log4jLogger can change RootLogger logging level unexpectedly. …n other loggers. You can merge this pull request into a Git repository by running: $ git pull

Re: Making News page more visible

Looks much better! Thanks for making that change. I've just joined the Apache Ignite community. Most of my career has been devoted to building and growing technical online communities. I'd be honored to help the Apache Ignite community grow via some modest social promotion, blogging -- anywhere I

[GitHub] ignite pull request #1628: IGNITE-4826: SQL: Eviction to swap failed if segm...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1628 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: IGNITE-4284 - ready for review

Its ok. I doing it for long time because I create branch from master. And I not saw ignite-4157 where appeared new events. 2017-03-28 16:59 GMT+03:00 Dmitry Karachentsev : > Hi Nikita, > > I've looked through the issue and, because fix is quite small and > important,

Re: IGNITE-4188, savepoints with atomic cache?

Ignore atomicCache.put(k, v) if it is called inside transaction? This is very counter intuitive. I am strongly against that. --Yakov

Re: IGNITE-4188, savepoints with atomic cache?

I mean ignore it in savepoints and rollbacks to savepoints becouse transaction rollbacks already ignore it. 2017-03-28 18:10 GMT+03:00 Yakov Zhdanov : > Ignore atomicCache.put(k, v) if it is called inside transaction? This is > very counter intuitive. I am strongly against

Re: distributed transaction of non-single coordinator

Hi, Igniters! I 've made implementation of transactions of non-single coordinator. Here you can start transaction in one thread and commit it in another thread. Take a look on it. Give your thoughts on it. https://github.com/voipp/ignite/pull/10/commits/3a3d90aa6ac84f125e4c3ce4ced4f269a695ef45

[jira] [Created] (IGNITE-4875) Allow execution over explicit set of partitions for every non-SQL query type with data integrity guarantees.

Alexei Scherbakov created IGNITE-4875: - Summary: Allow execution over explicit set of partitions for every non-SQL query type with data integrity guarantees. Key: IGNITE-4875 URL:

Fwd: [PMCs] Seeking your help for ASF's 18th Anniversary

Igniters, ASF needs you support. Please read below. Prachi, please add this logo to Ignite site’s footer and make it refer to the donation page [1]: https://blogs.apache.org/foundation/mediaresource/d67ca611-a57c-462d-ac23-95063f81d175

Re: distributed transaction of non-single coordinator

Aleksey, Do you have a ticket for this? Could you briefly list what exactly was done and how the things work. — Denis > On Mar 28, 2017, at 8:32 AM, ALEKSEY KUZNETSOV > wrote: > > Hi, Igniters! I 've made implementation of transactions of non-single > coordinator.

Re: IGNITE - 4760 : working in hibernate module

Denis, thank you for instruction. I've successfully applied it: 1) cloned project by my fork - https://github.com/vadopolski/ignite 2) created project from existing sources 3) built it - mvn clean package -DskipTests -Prelease,lgpl 4) created module from existing sources (import module from

Re: Making News page more visible

Hi Tom, Welcome to the community! It’s great we have contributor like you. BTW, what do you think on this? > Second, can we anchor every piece of news [1] so that it can be referred > directly from other sources. Also it makes sense to add “Twitter”, “FB”, > “LinkedIn” icons close to every

Re: [PMCs] Seeking your help for ASF's 18th Anniversary

Prachi, thanks! Merged. > On Mar 28, 2017, at 11:59 AM, Prachi Garg wrote: > > Denis, > > Please apply the attached patch. > > -P > > On Tue, Mar 28, 2017 at 9:34 AM, Denis Magda > wrote: > Igniters, > > ASF needs you

Re: Getting Started with Apache Ignite - Part 1

Dani, excellent job! *Prachi*, could you publish the article to DZone and update Ignite’s blogging page? Since this will be a series of posts don’t add DZone version of the article to Ignite’s page but rather add a link to the Dani’s own blog right away. *Dani*, to give more visibility to

Re: IGNITE-4188, savepoints with atomic cache?

If we want to make the exception based approach the default one then the task has to be released in 2.0. Dmitriy Ryabov, do you think you can finish it (dev, review, QA) by the code freeze data (April 14)? — Denis > On Mar 28, 2017, at 11:57 AM, Dmitriy Setrakyan

[GitHub] ignite pull request #1688: IGNITE-2786 : SpringCache doesn't survive client ...

GitHub user ryagnik opened a pull request: https://github.com/apache/ignite/pull/1688 IGNITE-2786 : SpringCache doesn't survive client reconnect The fix can be applied as follows with SpringCacheManager - 1) Design was to listen for ignite re connect event 2) And clear

Re: IGNITE-2766 Spring Cache Manager ReConnect Issue

Hi Val, Committed changes on IGNITE-2786, would like you to review the changes.Would you please review it ? Thanks, On Mon, Mar 27, 2017 at 6:11 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Rishi, > > You should be able to assign to tickets to yourself now. > > -Val > > On

Re: Adding ML to Ignite, IGNITE-4572

Unbelievable, that’s astonishing we can already release the distributed algebra support in the beta state. Please share the tasks you’re planning to work on right after the release. — Denis > On Mar 28, 2017, at 11:12 AM, nivanov wrote: > > Just a quick follow up... > >

Re: IGNITE-4188, savepoints with atomic cache?

I think an exception should be thrown if someone tries to start a transaction on an atomic cache. Throwing an exception at the "put(...)" time seems late and counter-intuitive. However, if a user starts a transaction on a transactional cache, say CacheA, and inside that transaction updates an

Re: Apache Ignite 2.0 Release

I think we can make it on time to add IgniteML (a.k.a. distributed math) to 2.0 release pipeline. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-0-Release-tp15690p15857.html Sent from the Apache Ignite Developers mailing list archive at

Re: IGNITE-4188, savepoints with atomic cache?

I actually think exception makes sense here. Currently it's very error prone - the same code can behave differently depending on configuration. And at the same time I can't imagine a use case which implies using atomic operation within a transaction on purpose. If someone ever does this, it would

Re: Adding ML to Ignite, IGNITE-4572

+100 Great feature! I too would like to see a list of tickets required for the release. D. On Tue, Mar 28, 2017 at 11:24 AM, Denis Magda wrote: > Unbelievable, that’s astonishing we can already release the distributed > algebra support in the beta state. Please share the

Re: IGNITE-4188, savepoints with atomic cache?

Dmitry, Transaction is not started on a particular cache, it's separate top-level API. You can then include operations on different caches, like this: try (Transaction tx = ignite.transactions.txStart()) { cache1.put(..); cache2.put(..); cache3.put(..); tx.commit(); } In the

Getting Started with Apache Ignite - Part 1

Hi Igniters, I'm working on a multi-part series on working with Apache Ignite and just released my first post today. This first post gives a conceptual basis to working with Ignite while follow up posts will work with code samples.

Re: Ignite-4795 - ready for review

Dmitry, see JIRA ticket for review comments. On Mon, Mar 27, 2017 at 6:13 PM, Denis Magda wrote: > Hello Dmitriy, thanks! Someone will have a look at your changes soon. Sorry > for the delay. > > — > Denis > >> On Mar 27, 2017, at 3:24 AM, Дмитрий Рябов

Re: Adding ML to Ignite, IGNITE-4572

Just a quick follow up... We've made some good progress on the initial code implementation in the last couple of months and I think we'll make it on time to release a early "beta" version of the IgniteML (a.k.a distributed math) for 2.0 release. -- View this message in context:

Re: Getting Started with Apache Ignite - Part 1

Very nice blog, really enjoyed reading it. On Tue, Mar 28, 2017 at 11:42 AM, Dani Traphagen wrote: > Hi Igniters, > > I'm working on a multi-part series on working with Apache Ignite and just > released my first post today. >

Re: Continuations for services

Vova, Take a look at GridJobProcessor#processJobExecuteRequest method. In particular, I'm talking about this piece of code: if (ctx.localNodeId().equals(node.id())) { // Always execute in another thread for local node. executeAsync(job); // No sync execution. job = null; }

Re: Getting Started with Apache Ignite - Part 1

Thanks Dmitriy! On Tue, Mar 28, 2017 at 11:48 AM Dmitriy Setrakyan wrote: > Very nice blog, really enjoyed reading it. > > On Tue, Mar 28, 2017 at 11:42 AM, Dani Traphagen > wrote: > > > Hi Igniters, > > > > I'm working on a multi-part series on

Re: [GridCachePartitionExchangeManager] Pending transaction deadlock detection futures

cross-posting to dev list. Guys, Does anyone have an idea why client mode in Visor affects behavior? I thought we already forced client mode there, no? Alexey, you should know the answer. Can you please take a look at this thread? -Val On Tue, Mar 28, 2017 at 7:02 AM, ght230

Re: IGNITE-4188, savepoints with atomic cache?

On Tue, Mar 28, 2017 at 11:42 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Dmitry, > > Transaction is not started on a particular cache, it's separate top-level > API. You can then include operations on different caches, like this: > > try (Transaction tx =

Re: IGNITE-4188, savepoints with atomic cache?

I think updating an Atomic cache from within a transaction perfectly makes sense. For example for some kind of operations logging and so forth. Still I agree that this can be error prone and forbidden by default. I agree with Yakov that by default we should throw an exception and have some kind of

Re: IGNITE-4188, savepoints with atomic cache?

On Tue, Mar 28, 2017 at 11:54 AM, Sergi Vladykin wrote: > I think updating an Atomic cache from within a transaction perfectly makes > sense. For example for some kind of operations logging and so forth. Still > I agree that this can be error prone and forbidden by

Re: [PMCs] Seeking your help for ASF's 18th Anniversary

Denis, Please apply the attached patch. -P On Tue, Mar 28, 2017 at 9:34 AM, Denis Magda wrote: > Igniters, > > ASF needs you support. Please read below. > > Prachi, please add this logo to Ignite site’s footer and make it refer to > the donation page [1]: >

Re: Adding ML to Ignite, IGNITE-4572

Hi, I am Alper. I am a computer engineering and mathematics (as double major) student with great interest in machine learning. I wish to participate in GSOC - 2017 and I've been interested in this "issue" for a while. I think that my skills fits this project and that I can really be useful and