Re: Batch DML queries design discussion

On Fri, Dec 9, 2016 at 12:45 AM, Vladimir Ozerov wrote: > I already expressed my concern - this is counterintuitive approach. Because > without happens-before pure streaming model can be applied only on > independent chunks of data. It mean that mentioned ETL use case is

Re: affinityCall in one distributed transaction

Sounds like you need a centralized JTA server for this type of purpose, no? In that case, Ignite transactions can already merge into ongoing JTA transactions. I would prefer to see a distributed flow of events to fully understand the issue. For example, Client - start transaction - send

Re: ignite-spark module in Hadoop Accelerator

On Fri, Dec 9, 2016 at 2:48 AM, Vladimir Ozerov wrote: > Dima, > > The idea is not to add libs to Hadoop Accelerator, but to remove > Accelerator edition altogether. Instead, we will add accelerator JARs to > fabric. > I get the idea, but I don't see it. If I just need

Re: Request to work on IGNITE-3878

Yes, exactly. However, this ticket has already been resolved https://issues.apache.org/jira/browse/IGNITE-3959 You can pick up the other one. For instance here we keep interesting and challenging tasks

Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

I see the same on my side [09:07:37] Ignite node started OK (id=a09edfc6) [09:07:42] Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=1.0GB] [09:07:47] New version is available at ignite.apache.org: 1.7.0 Did we miss something during the release stage? Sergey K., Vovan, could you

Re: Blogging about new .NET features

Excellent! Prachi, please post the blog on DZone. — Denis > On Dec 9, 2016, at 6:07 AM, Pavel Tupitsyn wrote: > > There you go: https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-1-8/ > > > On Wed, Nov 30,

[GitHub] ignite pull request #1338: IGNITE-4410 .NET: Provide default-config-dotnet.x...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1338 IGNITE-4410 .NET: Provide default-config-dotnet.xml You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-4410

[jira] [Created] (IGNITE-4410) .NET: Provide default-config-dotnet.xml

Pavel Tupitsyn created IGNITE-4410: -- Summary: .NET: Provide default-config-dotnet.xml Key: IGNITE-4410 URL: https://issues.apache.org/jira/browse/IGNITE-4410 Project: Ignite Issue Type:

[GitHub] ignite pull request #1337: IGNITE-4046: Implemented BinaryArrayIdentityResol...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1337 IGNITE-4046: Implemented BinaryArrayIdentityResolver. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-4046

Re: Blogging about new .NET features

There you go: https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-1-8/ On Wed, Nov 30, 2016 at 4:35 AM, Denis Magda wrote: > Cos, > > This sounds interesting. Did it help to promote BigTop somehow? > > As I understand the blogging engine lacks of advanced text and code >

Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

Hi Maven repository has been released. https://repository.apache.org/content/repositories/releases/org/apache/ignite/ On Fri, Dec 9, 2016 at 4:41 PM, 李玉珏@163 <18624049...@163.com> wrote: > maven repo is not updated? > > > > 在 2016/12/9 21:37, Ксения Рыбакова 写道: > >> Hi, >> >> Update notifier

[GitHub] ignite pull request #1336: IGNITE-4264: Offheap cache entries statistics is ...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1336 IGNITE-4264: Offheap cache entries statistics is broken in master Fixed. You can merge this pull request into a Git repository by running: $ git pull

Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

maven repo is not updated? 在 2016/12/9 21:37, Ксения Рыбакова 写道: Hi, Update notifier for 1.7.0 shows that version is up to date. Could anybody fix it please? +--+ Ignite ver.

Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

Hi, Update notifier for 1.7.0 shows that version is up to date. Could anybody fix it please? >>> +--+ >>> Ignite ver. 1.7.0#20160801-sha1:383273e3f66f702de2482466dce954d570a8ccf2 >>>

Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

I've updated the site, there were commented parts on Download page from Denis, so that was easy :) Main and News pages also updated. Just a reminder - any committer can update the site, just modify files in SVN, and changes will appear online: https://svn.apache.org/repos/asf/ignite/site/trunk

[jira] [Created] (IGNITE-4409) UUID fields of the key class deserialized in a wrong way on INSERT.

Igor Sapego created IGNITE-4409: --- Summary: UUID fields of the key class deserialized in a wrong way on INSERT. Key: IGNITE-4409 URL: https://issues.apache.org/jira/browse/IGNITE-4409 Project: Ignite

[jira] [Created] (IGNITE-4408) IndexingSpi support keepBinary options

Andrew Mashenkov created IGNITE-4408: Summary: IndexingSpi support keepBinary options Key: IGNITE-4408 URL: https://issues.apache.org/jira/browse/IGNITE-4408 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4407) IgniteUuid is a single point of contention for the whole framework.

Vladimir Ozerov created IGNITE-4407: --- Summary: IgniteUuid is a single point of contention for the whole framework. Key: IGNITE-4407 URL: https://issues.apache.org/jira/browse/IGNITE-4407 Project:

Re: ignite-spark module in Hadoop Accelerator

Dima, The idea is not to add libs to Hadoop Accelerator, but to remove Accelerator edition altogether. Instead, we will add accelerator JARs to fabric. On Fri, Dec 9, 2016 at 4:45 AM, Dmitriy Setrakyan wrote: > Guys, again, Hadoop edition is for *plug-n-play* Hadoop

Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

Denis, Release has been propagated to mirrors, so you can go ahead with site update. Vladimir. On Fri, Dec 9, 2016 at 1:28 AM, Denis Magda wrote: > Great, thanks! > > Released all the docs (Java, .NET, C++, etc.) and update the site > partially. > > I can’t go ahead and

Re: affinityCall in one distributed transaction

In some cases it is necessary to implement a transaction processing logic in several different application servers. In this case, working with Ignite cache will be performed within the various applications. But all these changes must be made within the same distributed transaction. In my opinion

[jira] [Created] (IGNITE-4406) .NET: Control DateTime serialization via attribute

Pavel Tupitsyn created IGNITE-4406: -- Summary: .NET: Control DateTime serialization via attribute Key: IGNITE-4406 URL: https://issues.apache.org/jira/browse/IGNITE-4406 Project: Ignite

[GitHub] ignite pull request #1334: IGNITE-4270

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

[jira] [Created] (IGNITE-4405) Hadoop: support "readLine" method in HadoopDataInStream and HadoopDirectDataInput classes.

Vladimir Ozerov created IGNITE-4405: --- Summary: Hadoop: support "readLine" method in HadoopDataInStream and HadoopDirectDataInput classes. Key: IGNITE-4405 URL: https://issues.apache.org/jira/browse/IGNITE-4405

Re: Batch DML queries design discussion

I already expressed my concern - this is counterintuitive approach. Because without happens-before pure streaming model can be applied only on independent chunks of data. It mean that mentioned ETL use case is not feasible - ETL always depend on implicit or explicit links between tables, and hence

Re: Batch DML queries design discussion

I already expressed my concern - this is counterintuitive approach. Because without happens-before pure streaming model can be applied only on independent chunks of data. It mean that mentioned ETL use case is not feasible - ETL always depend on implicit or explicit links between tables, and hence

Re: DML Documentation Readiness

Denis, About your question: 'putIfAbsent' is used only when we have single key-value pair to process as long as we don't have method like 'put all if absent'. When there's a bunch of pairs, an entry processor is created for each pair to make its processing atomic (effectively CAS style

[jira] [Created] (IGNITE-4404) GridCacheOffHeapMultiThreadedUpdateAbstractSelfTest long running test refactoring

Konstantin Dudkov created IGNITE-4404: - Summary: GridCacheOffHeapMultiThreadedUpdateAbstractSelfTest long running test refactoring Key: IGNITE-4404 URL: https://issues.apache.org/jira/browse/IGNITE-4404

[jira] [Created] (IGNITE-4403) IgniteCacheQueryMultiThreadedSelfTest long running test refactoring

Konstantin Dudkov created IGNITE-4403: - Summary: IgniteCacheQueryMultiThreadedSelfTest long running test refactoring Key: IGNITE-4403 URL: https://issues.apache.org/jira/browse/IGNITE-4403