Re: Transaction semantics questions

+ My 5 cents: When a transaction uses one-phase commit optimization, there is no difference between PRIMARY_SYNC and FULL_SYNC. 2017-02-08 21:50 GMT+03:00 Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Thanks! > > -Val > > On Tue, Feb 7, 2017 at 8:43 PM, Yakov Zhdanov

[jira] [Created] (IGNITE-4676) Clojure hangs if executed nested internal task with continuation

Alexey Kuznetsov created IGNITE-4676: Summary: Clojure hangs if executed nested internal task with continuation Key: IGNITE-4676 URL: https://issues.apache.org/jira/browse/IGNITE-4676 Project:

Re: DML & Transactions

On Wed, Feb 8, 2017 at 10:20 PM, Yakov Zhdanov wrote: > Guys, I think we should explicitly state this on readme.io - Do not use > DML > within transactions. > > And probably throw an exception on such attempts. > Absolutely agree. I would say that DML within transactions is

Re: DML & Transactions

Guys, I think we should explicitly state this on readme.io - Do not use DML within transactions. And probably throw an exception on such attempts. --Yakov 2017-02-09 12:08 GMT+07:00 Sergi Vladykin : > Not yet, we need MVCC over PageMemory for this. Probably it will

Re: jdbc vs jdbc2 packages

Val, 1. Our clients should stop require persistent store implementation if they do not need it. Can you please file a ticket? I know you fixed some places already. As an idea I would keep everything in binary format until we really need it. Will that work? 2. We can try adding the very first step

[jira] [Created] (IGNITE-4675) Make client node to fetch configuration from server (i.e. connect only by address:port)

Yakov Zhdanov created IGNITE-4675: - Summary: Make client node to fetch configuration from server (i.e. connect only by address:port) Key: IGNITE-4675 URL: https://issues.apache.org/jira/browse/IGNITE-4675

Re: DML & Transactions

Not yet, we need MVCC over PageMemory for this. Probably it will arrive in some 2.x version. Sergi 2017-02-09 7:42 GMT+03:00 Yakov Zhdanov : > Guys (esp Alex P and Sergi), > > Do we preserve transactional semantics of updates? > > In other words, does the following make

DML & Transactions

Guys (esp Alex P and Sergi), Do we preserve transactional semantics of updates? In other words, does the following make sense? and when it does not? startTx() insert into blabla... update bla bla... commit() --Yakov

Re: Binary objects and cache store

+1 -Val On Wed, Feb 8, 2017 at 4:57 PM, Denis Magda wrote: > Cross-posting to the dev list. > > Igniters, what if we make “storeKeepBinary” = true by default in Ignite > 2.0? Presently, the user has to tweak the configuration manually. > > — > Denis > > On Feb 7, 2017, at

Re: DML data streaming

Alexander, Are you suggesting that currently to execute a simple INSERT for 1 row we invoke a data streamer on Ignite API? How about an update by a primary key? Why not execute a simple cache put in either case? I think we had a separate thread where we agreed that the streamer should only be

Re: ScanQuery shows poor performance.

Alexey, Would you please look at PR [1]; Can it be fixed the way implemented at PR or I've missed smth? [1] https://issues.apache.org/jira/browse/IGNITE-4624 On Fri, Jan 27, 2017 at 7:57 PM, Dmitriy Setrakyan wrote: > On Fri, Jan 27, 2017 at 7:03 AM, Alexey Goncharuk <

Re: Test failures

I also agree. I think we should create tickets for all failing tests and have the community grab them. On Wed, Feb 8, 2017 at 5:50 AM, Александр Меньшиков wrote: > +1 to Aleksey, Alexander and Vyacheslav. > > I suppose that the best option is make issue for every

Re: Transaction semantics questions

Thanks! -Val On Tue, Feb 7, 2017 at 8:43 PM, Yakov Zhdanov wrote: > Val, I think value read which is about to be overwritten by a commit is > possible. I think only pessimistic repeatable read tx can protect you > against that. Also, it seems there are no difference

[GitHub] ignite pull request #1441: IGNITE-3537

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1441 --- 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: DML data streaming

Hi Alexander. What's about supporting statement *INSERT INTO ... SELECT FROM* for streams? Does it make sense? On Wed, Feb 8, 2017 at 6:44 PM, Alexander Paschenko < alexander.a.pasche...@gmail.com> wrote: > Also, currently it's possible to run SELECTs on "streamed" > connections, and probably

[GitHub] ignite pull request #1508: IGNITE-4523 Allow distributed SQL query execution...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/1508 IGNITE-4523 Allow distributed SQL query execution over explicit set of partitions You can merge this pull request into a Git repository by running: $ git pull

Re: DML data streaming

Also, currently it's possible to run SELECTs on "streamed" connections, and probably this is odd and should not be released too, what do you think? - Alex 2017-02-08 18:00 GMT+03:00 Alexander Paschenko : > Hello Igniters, > > I'd like to raise few questions

[jira] [Created] (IGNITE-4673) Object array element type is written as a user type

Pavel Tupitsyn created IGNITE-4673: -- Summary: Object array element type is written as a user type Key: IGNITE-4673 URL: https://issues.apache.org/jira/browse/IGNITE-4673 Project: Ignite

DML data streaming

Hello Igniters, I'd like to raise few questions regarding data streaming via DML statements. Currently, all types of DML statements are supported (INSERT, UPDATE, DELETE, MERGE). UPDATE and DELETE are supported in streaming mode only when their WHERE condition is bounded with _key and/or _val

[jira] [Created] (IGNITE-4672) Optimization: for SQL indexes implement comparison using offheap pointer

Semen Boikov created IGNITE-4672: Summary: Optimization: for SQL indexes implement comparison using offheap pointer Key: IGNITE-4672 URL: https://issues.apache.org/jira/browse/IGNITE-4672 Project:

[jira] [Created] (IGNITE-4671) FairAffinityFunction fails on node restart with backupFilter set and no backups

Dmitry Karachentsev created IGNITE-4671: --- Summary: FairAffinityFunction fails on node restart with backupFilter set and no backups Key: IGNITE-4671 URL: https://issues.apache.org/jira/browse/IGNITE-4671

[jira] [Created] (IGNITE-4670) CPP: Implement LoadCache method

Igor Sapego created IGNITE-4670: --- Summary: CPP: Implement LoadCache method Key: IGNITE-4670 URL: https://issues.apache.org/jira/browse/IGNITE-4670 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #1484: IGNITE-4631 Added check to ensure QueryEntity 'ke...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1484 --- 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

FINAL REMINDER: CFP for ApacheCon closes February 11th

Dear Apache Enthusiast, This is your FINAL reminder that the Call for Papers (CFP) for ApacheCon Miami is closing this weekend - February 11th. This is your final opportunity to submit a talk for consideration at this event. This year, we are running several mini conferences in conjunction with

Re: Test failures

+1 to Aleksey, Alexander and Vyacheslav. I suppose that the best option is make issue for every master-failed-test. And fix them all. Floating tests should be normal. I think in most case we can just add repeating. All new test for some not ready future should be marked like "Should be fix in

[GitHub] ignite pull request #1507: IGNITE-4663: skip class loading when deserialize ...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1507 IGNITE-4663: skip class loading when deserialize == false You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Test failures

I vote for the master-branche without failed-tests) I understand that impossible to make it quickly. We shall aim at this approach. It will be more comfortable to us to develop. 2017-02-08 12:17 GMT+03:00 Alexander Fedotov : > Hi, > > I would agree with Aleksey.

[jira] [Created] (IGNITE-4669) .NET: Sort binary object fields

Pavel Tupitsyn created IGNITE-4669: -- Summary: .NET: Sort binary object fields Key: IGNITE-4669 URL: https://issues.apache.org/jira/browse/IGNITE-4669 Project: Ignite Issue Type: Improvement

[GitHub] ignite pull request #1492: IGNITE-4619 .NET: TransactionScope example

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1492 --- 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: Test failures

Hi, I would agree with Aleksey. >From the CI perspective, failing tests should be the main concern, because it prevents a durable development of new features. Also, as Aleksey has noted, developers working on different features could end up fixing the same regressions, chances are - in different

[GitHub] ignite pull request #1506: IGNITE-4302 binary metadata component refactored ...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1506 IGNITE-4302 binary metadata component refactored to use discovery-based protocol Metadata updates are exchanged using DiscoveryCustomMessage-based protocol instead of utility cache.

[GitHub] ignite pull request #1505: IGNITE-3244 Custom arrays arent serialized proper...

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/1505 IGNITE-3244 Custom arrays arent serialized properly arrays type now considered while deserialization. After deserialization you've got array of correct type You can merge this pull request into a