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 wrote: > > > Val,

[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: Ign

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 not supported yet. We

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 arrive in > some 2.x version.

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 sense? and when it does n

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 10:30 PM, shawn.du wr

[GitHub] ignite pull request #1510: IGNITE-4226: Redis SET command to handle expirati...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/1510 IGNITE-4226: Redis SET command to handle expirations. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-4226 Alternatively

Binary objects and cache store

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 10:30 PM, shawn.du wrote: > > get it. > > storeKeepBinary flag will help. > > Thanks > Shaw

Re: Patches for Website

Hi Mauricio, Could you go to the trunk folder of your clone and make the patch from there? Presently I can’t merge the changes getting this kind of error: Skipped missing target: 'site/trunk/use-cases/hadoop/hdfs-cache.html' Skipped missing target: 'site/trunk/use-cases/hadoop/mapreduce.html' Sk

Re: Feedback on Web Console usage

Apart from all the issues listed by Denis, I would say that DML and the upcoming DDL should be enabled in the Web Console. Otherwise SQL support just seems incomplete. Is this difficult to add? D. On Wed, Feb 8, 2017 at 3:48 PM, Denis Magda wrote: > Alex K., > > As a part of preparations to th

Feedback on Web Console usage

Alex K., As a part of preparations to the upcoming Web Console related webinar I faced with a couple usability issues. *DML* Not supported at the moment. I’ve created a ticket and propose to release it in 1.9 (https://issues.apache.org/jira/browse/IGNITE-4674

[jira] [Created] (IGNITE-4674) Ignite Web Console: Support DML queries

Denis Magda created IGNITE-4674: --- Summary: Ignite Web Console: Support DML queries Key: IGNITE-4674 URL: https://issues.apache.org/jira/browse/IGNITE-4674 Project: Ignite Issue Type: Task

Re: jdbc vs jdbc2 packages

Yakov, I agree that investing in the legacy client doesn't make sense - it's slow and outdated. Regarding your points: 1. This is just another build step, but the JAR is going to pretty fat I think (it will have to include Spring). Not ideal, but definitely better than what we have now. However,

Re: IGNITE-3244

Generally, this code is correct. marshalToBinary must return array of BinaryObject instances when object array is passes as an input. However, the fact that we convert even first class citizen arrays (e.g. String[]) looks wrong. Perhaps we need to check that and return arrays like this as-is, witho

Re: Test failures

> How could they co-exist ? When you developing some ticket you are risking > introduce bug which is reproduced by already failed test(s). Because there is no IT project that is bug-free. In my experience, it’s a usual situation when a part of the system is being evolved while the other is being

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 tur

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 < > alexey.goncha...@gmail

[GitHub] ignite pull request #1509: IGNITE-4624: ScanQuery shows poor performance.

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1509 IGNITE-4624: ScanQuery shows poor performance. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4624 Alternati

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 master-failed-test. > And fix th

Re: Sort nodes in the ring in order to minimize the number of reconnections

Done. Please look. JIRA: https://issues.apache.org/jira/browse/IGNITE-4501 PR: https://github.com/apache/ignite/pull/1436/files Tests: http://ci.ignite.apache.org/project.html?projectId=IgniteTes ts&tab=projectOverview&branch_IgniteTests=pull/1436/head

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 between read from one > node

[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 ena

Re: IGNITE-3244

Hi Aleksey, >> type IDs correctly attached to class descriptors. The issue comes from >> BinaryUtils#doReadObjectArray() . Presently, unmarshalled array's elements >> stored in Object[], one need to write the following : >> Object[] arr = (Object[])Array.newInstance(compType, len); >> instead of >

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 t

[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 https://github.com/gridgai

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 regarding data streaming via DML statem

[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 Issu

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 co

[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: Ign

[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 Com

[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 ena

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 t

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 IG

[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 ignit

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. > From the CI perspective, fail

[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 ena

[jira] [Created] (IGNITE-4668) Doesn't work "manual" yardsticks when ip of server/driver not equal ip of ethernet interface

Ilya Suntsov created IGNITE-4668: Summary: Doesn't work "manual" yardsticks when ip of server/driver not equal ip of ethernet interface Key: IGNITE-4668 URL: https://issues.apache.org/jira/browse/IGNITE-4668

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 w

[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 Gi