Re: Transactional tasks

>> This is prefectly valid. Second transaction'll wait for completion of first. Alex S., I think you did not get the point. It seems AG meant two jobs of the same task, so it is one TX. It is unclear to me how to resolve this automatically. I would agree with AG and permit only primary keys local

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

Hi Oleg, Great progress, thanks for keep driving this! I’ve left some minor notes in GitHub’s pull-request. I have the following questions aside: - What is the difference between "Building from standalone sources" and "Building from Ignite Sources"? In my understanding, a user downloads

Re: How to improve SQL testing

Hi, That’s true that the utility/testing framework needs to be as flexible as possible. If the community can’t reuse an existing one let’s make it up. As for VoltDB SQL Coverage Suite, if it’s Python based then can we implement those Python APIs directly calling Ignite.C++? — Denis > On Jan

Re: Transactional tasks

Alexey, Every job is executed in transaction having same semantics as any other transaction, but transaction is managed by Ignite transparently. Job's transaction is rolled back on throwing any unchecked exception or special TransactionRollbackException. Concurrency issues between jobs are

Re: moving to geronimo JCache jar

Alexander, thanks! I’ll review it in the nearest couple of days. — Denis > On Jan 30, 2017, at 5:10 AM, Alexander Fedotov > wrote: > > Hi, > > Created Upsource review for the subject: > http://reviews.ignite.apache.org/ignite/review/IGNT-CR-82 > > On Mon, Jan

Re: newbie ticket issue

Yes, according to other discussion you were successfully added. — Dens > On Jan 30, 2017, at 1:03 AM, ALEKSEY KUZNETSOV > wrote: > > Hi! My JIRA ID : > https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Alexey+Kuznetsov > > пт, 27 янв. 2017 г. в 20:52,

Re: Python Platform for Ignite

Hi Shanshank, I’ve prepared tickets related to this activity: https://issues.apache.org/jira/browse/IGNITE-4600 I would agree that if we want to be as generic as possible then we need to write our own implementation rather relying on SWIG. So,

[GitHub] ignite pull request #1454: Ignite 4003 1.7 no drop

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/1454 --- 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: Unused variables in code

Done. My PR: https://github.com/apache/ignite/pull/1466/files 2017-01-25 13:11 GMT+03:00 Александр Меньшиков : > Okay, I created issue: > https://issues.apache.org/jira/browse/IGNITE-4612 > > > 2017-01-24 18:19 GMT+03:00

Review for IGNITE-4436 API to collect list of running SQL queries

Hi All! I prepared first version https://issues.apache.org/jira/browse/IGNITE-4436 (SQL: create API to collect list of running SQL queries and cancel them). Please review it and give a feedback: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-84 But also I have following questions: 1)

Re: IGNITE-1948 ClusterTopologyCheckedException can return null for retryReadyFuture()

Okay, it seems good. So you want to remove field *readyFut* from *ClusterTopologyCheckedException* and add *CacheTopologyCheckedException* like *ClusterTopologyCheckedException* but initialize *readyFut* in constructor, yes? 2017-01-30 16:54 GMT+03:00 Alexey Goncharuk

Re: IGNITE-1948 ClusterTopologyCheckedException can return null for retryReadyFuture()

In the example above there is no point of setting the retry future in the exception because it will be serialized and sent to a remote node. I see the only possible way to ensure this: make this be verified at compile time. This looks like a big change, but the draft may look like so: 1)

Re: IgniteConfiguration.gridName is very confusing

Done. But it looks like something went wrong since Upsource reports: "Review has too many files (1244), aborting". Also guys, I believe we need to merge this change in short time because it's targeted for 2.0 and chances for a conflict are high. On Mon, Jan 30, 2017 at 4:16 PM, Pavel Tupitsyn

[GitHub] ignite pull request #1480: IGNITE-4444 Extend .NET plugin API to interact wi...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1480 IGNITE- Extend .NET plugin API to interact with Java You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-

Re: IgniteConfiguration.gridName is very confusing

Alexander, Please name the review appropriately and link it in the ticket as described: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewWithUpsource Thanks, Pavel On Mon, Jan 30, 2017 at 4:00 PM, Alexander Fedotov < alexander.fedot...@gmail.com> wrote:

Re: moving to geronimo JCache jar

Hi, Created Upsource review for the subject: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-82 On Mon, Jan 30, 2017 at 11:52 AM, Alexander Fedotov < alexander.fedot...@gmail.com> wrote: > Hi all, > > https://issues.apache.org/jira/browse/IGNITE-3793 is completed. > Kindly take a look at

Re: IgniteConfiguration.gridName is very confusing

Hi, Created Upsource review for the subject: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-81 On Thu, Jan 19, 2017 at 7:59 PM, Alexander Fedotov < alexander.fedot...@gmail.com> wrote: > Hi, > > I've completed working on IGNITE-3207 > https://issues.apache.org/jira/browse/IGNITE-3207 >

Ignite-2.0 - Make near readers update async by default

Guys, Currently when we do cache updates in FULL_SYNC mode we update near readers (near cache entries) synchronously. This is quite big drawback in design, I think. I get each near reader update at cost of 1 extra backup update. I think everyone understands that partitioned cache easily turns to

Re: How to improve SQL testing

Sergey, Could we use http://www.jython.org/ to make it works as-is? On Mon, Jan 30, 2017 at 6:06 PM, Sergey Kozlov wrote: > Hi > > Hi reviewed the links below (thanks for Vova Ozerov to pointing me) and > found that the provided solution is really excellent! >

Re: IGNITE-1948 ClusterTopologyCheckedException can return null for retryReadyFuture()

Alexey, For GridCacheIoManager#sendNoRetry it's not necessary because exception will be ignored (or will cast to String). Perhaps my message was unclear. I try to say that three methods can throw "ClusterTopologyCheckedException" without any problem. But you are right, in some methods I can't

[GitHub] ignite pull request #1479: IGNITE-4533 GridDhtPartitionsExchangeFuture store...

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/1479 IGNITE-4533 GridDhtPartitionsExchangeFuture stores unnecessary messag… …es after processing done You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1478: ignite-4626

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

[GitHub] ignite pull request #1477: IGNITE-4492 Add MBean for StripedExecutor

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/1477 IGNITE-4492 Add MBean for StripedExecutor Added MBean for StripedExecutor You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite

IGNITE-3196 - ready for review

Hello. I fixed it. Please, review. https://issues.apache.org/jira/browse/IGNITE-3196 - Marshaling works wrong for the BigDecimals that have negative scale

Re: IGNITE-1948 ClusterTopologyCheckedException can return null for retryReadyFuture()

Alexander, Do you have a use-case in mind which results in IgniteTopologyException thrown from public API with retryFuture unset? retryFuture makes sense only for certain cache operations and may be set only in certain places in the code where we already know what to wait for. I do not see how

Re: IGNITE-4492

thanx пт, 27 янв. 2017 г. в 17:15, Alexey Kuznetsov : > Added to contributors. > > On Fri, Jan 27, 2017 at 9:04 PM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com > > wrote: > > > https://issues.apache.org/jira/secure/ViewProfile.jspa? > > name=Alexey+Kuznetsov > > > > пт,

Re: newbie ticket issue

Hi! My JIRA ID : https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Alexey+Kuznetsov пт, 27 янв. 2017 г. в 20:52, Denis Magda : > + dev list > > > On Jan 27, 2017, at 9:52 AM, Denis Magda wrote: > > > > Hello Aleksey, > > > > Welcome to the Ignite

Re: moving to geronimo JCache jar

Hi all, https://issues.apache.org/jira/browse/IGNITE-3793 is completed. Kindly take a look at the corresponding PR https://github.com/apache/ ignite/pull/1475 . On Wed, Jan 25, 2017 at 8:04 PM, Denis Magda wrote: > We need to replace content of ignite-core-licenses.txt file