Re: Dedicated readme.io documentation for Ignite integrations

Roman, The access is granted. — Denis > On Dec 4, 2016, at 6:37 PM, Roman Shtykh wrote: > > Denis, > > Can you please set permissions for me to edit > https://apacheignite-mix.readme.io/docs? > > -Roman > > > > On Thursday, December 1, 2016 4:38 PM, Dmitriy

[GitHub] ignite pull request #1318: Ignite 4003

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/1318 Ignite 4003 You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-4003 Alternatively you can review and apply these

Re: [VOTE] Apache Ignite 1.8.0 RC1

+1 (binding) — Denis > On Dec 5, 2016, at 7:22 AM, Vladimir Ozerov wrote: > > Hello, > > We have uploaded the 1.8.0 release candidate to > *https://dist.apache.org/repos/dist/dev/ignite/1.8.0-rc1/ > * > > Tag

Re: [DISCUSS] PMC Chair rotation time

I haven't forgotten. Just got back from a business trip. Will start a vote this week. On Wed, Nov 23, 2016 at 5:18 PM, Dmitriy Setrakyan wrote: > Cos, I will start the vote soon. A bit over occupied with travel and > holidays at this moment. > > On Mon, Nov 21, 2016 at

Re: [VOTE] Apache Ignite 1.8.0 RC1

+1 (binding) -Roman On Tuesday, December 6, 2016 8:14 AM, Denis Magda wrote: +1 (binding) — Denis > On Dec 5, 2016, at 7:22 AM, Vladimir Ozerov wrote: > > Hello, > > We have uploaded the 1.8.0 release candidate to >

[jira] [Created] (IGNITE-4371) Neat TX finish request processing may fall into sync wait of dht finish response

Yakov Zhdanov created IGNITE-4371: - Summary: Neat TX finish request processing may fall into sync wait of dht finish response Key: IGNITE-4371 URL: https://issues.apache.org/jira/browse/IGNITE-4371

Re: SQL query CPU utilization too low.

Copy from Review comment >Sergi: Another thing is how we will handle case if different caches in join have different parallelism level? Good question, Sergi. It seems we can't handle it. I've a crazy idea and not sure it is workable. What if we would split indices to power of 2 number of segments

Re: SQL query CPU utilization too low.

I'd prefer to avoid merging ranges from index segments, it is a huge performance penalty. I thought a bit more: why would one configure a different level of query parallelism on different caches? I don't see any sane reason for this. Most probably it will be a number of CPU cores on the box or

[GitHub] ignite pull request #1304: IGNITE-4343 DmlStatementsProcessor - entry proces...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1304 --- 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 #1275: IGNITE-4280 Test fix for IgniteBinaryCacheQueryTe...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1275 --- 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 #1293: IGNITE-4017 DML example.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1293 --- 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 #1286: IGNITE-4308 Ignore QueryEntity.keyFields when key...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1286 --- 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 #1280: IGNITE-4287 DmlStatementsProcessor logic fix

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1280 --- 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 #1269: IGNITE-3910: Implemented SQLDescribeParam.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1269 --- 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 #1272: IGNITE-4288: Fix for ignite-1.8.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1272 --- 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 #1291: IGNITE-4319 Test fix

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1291 --- 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 #1284: IGNITE-4279 Fix for testFetchSize in JdbcResultSe...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1284 --- 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 #1178: IGNITE-4096: Added ODBC tests for DML.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1178 --- 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 #1277: IGNITE-4299: Fixes for examples.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1277 --- 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 #1305: IGNITE-4347: Fixed NPE.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1305 --- 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 #1265: IGNITE-4016: IGNITE-4016: ODBC example now uses D...

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

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1313 --- 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 #1310: IGNITE-4355: (1) double checked locking in Hadoop...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1310 --- 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 #1314: IGNITE-4369 ReentranLocks hands on unlock when no...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1314 IGNITE-4369 ReentranLocks hands on unlock when node is stopped. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1289: IGNITE-4026 - Fix BinaryObjectBuilder.build() can...

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

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

[jira] [Created] (IGNITE-4367) .NET: Fix flaky tests

Pavel Tupitsyn created IGNITE-4367: -- Summary: .NET: Fix flaky tests Key: IGNITE-4367 URL: https://issues.apache.org/jira/browse/IGNITE-4367 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #1312: IGNITE-4271

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1312 --- 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-4369) ReentranLocks hands on unlock when node is stopped.

Taras Ledkov created IGNITE-4369: Summary: ReentranLocks hands on unlock when node is stopped. Key: IGNITE-4369 URL: https://issues.apache.org/jira/browse/IGNITE-4369 Project: Ignite Issue

[GitHub] ignite pull request #1282: IGNITE-4295

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1282 --- 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-4368) Data Streamer closed exception in Kafka Streamer

Anil created IGNITE-4368: Summary: Data Streamer closed exception in Kafka Streamer Key: IGNITE-4368 URL: https://issues.apache.org/jira/browse/IGNITE-4368 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #1281: Ignite 4026

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1281 --- 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 #1303: IGNITE-4340 Convert results of sub SELECTs to exp...

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

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/1313 IGNITE-4355 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4355-1 Alternatively you can review and apply

[jira] [Created] (IGNITE-4366) deadlock in continuous queries

Yakov Zhdanov created IGNITE-4366: - Summary: deadlock in continuous queries Key: IGNITE-4366 URL: https://issues.apache.org/jira/browse/IGNITE-4366 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-4365) Data grid in deadlock on stop

Yakov Zhdanov created IGNITE-4365: - Summary: Data grid in deadlock on stop Key: IGNITE-4365 URL: https://issues.apache.org/jira/browse/IGNITE-4365 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #1311: ignite-1.7.4

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

[GitHub] ignite pull request #1315: IGNITE-4281

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/1315 IGNITE-4281 …her optimizations. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4281 Alternatively you can

[GitHub] ignite pull request #1315: IGNITE-4281

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

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

[jira] [Created] (IGNITE-4370) ODBC: Implement DML operations with parameters in batch.

Igor Sapego created IGNITE-4370: --- Summary: ODBC: Implement DML operations with parameters in batch. Key: IGNITE-4370 URL: https://issues.apache.org/jira/browse/IGNITE-4370 Project: Ignite

[VOTE] Apache Ignite 1.8.0 RC1

Hello, We have uploaded the 1.8.0 release candidate to *https://dist.apache.org/repos/dist/dev/ignite/1.8.0-rc1/ * Tag name is 1.8.0-rc1 This release includes the following changes: Ignite: * SQL: Added DML operations support (INSERT,

[GitHub] ignite pull request #1317: IGNITE-3292 Yardstick: add logging of preloading ...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/1317 IGNITE-3292 Yardstick: add logging of preloading progress You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite