Re: Apache Ignite 2.7 release

Hello, Pavel. IGNITE-6055 merged to master. Please, update your code accordingly. You can take edits in CPP, .Net, NodeJS thin clients as example. В Пт, 24/08/2018 в 21:49 +0300, Nikolay Izhikov пишет: > PR is fully ready. > > I'm waiting final approve from Vladimir Ozerov. > > Hope, This will

[GitHub] ignite pull request #3973: IGNITE-6055: SQL: Add String length constraint

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3973 ---

Re: Apache Ignite 2.7 release

Thank you, Nikolay. Will do. p. On Tue, Aug 28, 2018 at 12:05 AM, Nikolay Izhikov wrote: > Hello, Pavel. > > IGNITE-6055 merged to master. > > Please, update your code accordingly. > You can take edits in CPP, .Net, NodeJS thin clients as example. > > В Пт, 24/08/2018 в 21:49 +0300, Nikolay Izh

[GitHub] ignite pull request #4630: IGNITE-9319 added extra log when cache have been ...

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/4630 IGNITE-9319 added extra log when cache have been empty You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9319 Alte

[GitHub] ignite pull request #4610: IGNITE-9362 SQL: Remove NODES.IS_LOCAL attribute

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4610 ---

[jira] [Created] (IGNITE-9394) MVCC: pds corrupted after grid restart.

Andrew Mashenkov created IGNITE-9394: Summary: MVCC: pds corrupted after grid restart. Key: IGNITE-9394 URL: https://issues.apache.org/jira/browse/IGNITE-9394 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-9395) Incorrect link to javadoc

Yury Gerzhedovich created IGNITE-9395: - Summary: Incorrect link to javadoc Key: IGNITE-9395 URL: https://issues.apache.org/jira/browse/IGNITE-9395 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #4628: IGNITE-9393: Fixed bug in reduce function in data...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4628 ---

[GitHub] ignite pull request #4621: IGNITE-9367 CPP: ODBC client crashes after execut...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4621 ---

[GitHub] ignite pull request #4631: Ignite-8149-2-merged-tc

GitHub user pavlukhin opened a pull request: https://github.com/apache/ignite/pull/4631 Ignite-8149-2-merged-tc For Team City. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8149-2-merged-tc Alterna

[GitHub] ignite pull request #4632: IGNITE-9312 Remove unnecessary @SuppressWarnings ...

GitHub user ololo3000 opened a pull request: https://github.com/apache/ignite/pull/4632 IGNITE-9312 Remove unnecessary @SuppressWarnings annotation You can merge this pull request into a Git repository by running: $ git pull https://github.com/ololo3000/ignite IGNITE-9312 Alt

[jira] [Created] (IGNITE-9396) ML Examples: can't run examples, not enough dependencies in pom.xml

Stepan Pilschikov created IGNITE-9396: - Summary: ML Examples: can't run examples, not enough dependencies in pom.xml Key: IGNITE-9396 URL: https://issues.apache.org/jira/browse/IGNITE-9396 Project

[jira] [Created] (IGNITE-9397) IgniteSqlDeleteBenchmark fails to run with java.util.NoSuchElementException

Ivan Artukhov created IGNITE-9397: - Summary: IgniteSqlDeleteBenchmark fails to run with java.util.NoSuchElementException Key: IGNITE-9397 URL: https://issues.apache.org/jira/browse/IGNITE-9397 Project

Ignite new contributor

Hi Team, I'd like to join to Apache Ignite development. Especially to the ML part. Currently, I work on IGNITE-9285 and I'm going to continue work with subtasks from IGNITE-9281 (ML starter task

[jira] [Created] (IGNITE-9398) Reduce time on processing CustomDiscoveryMessage by discovery worker

Pavel Kovalenko created IGNITE-9398: --- Summary: Reduce time on processing CustomDiscoveryMessage by discovery worker Key: IGNITE-9398 URL: https://issues.apache.org/jira/browse/IGNITE-9398 Project: I

[jira] [Created] (IGNITE-9399) Document new WAL history size configuration parameter

Alexey Goncharuk created IGNITE-9399: Summary: Document new WAL history size configuration parameter Key: IGNITE-9399 URL: https://issues.apache.org/jira/browse/IGNITE-9399 Project: Ignite

[GitHub] ignite pull request #4626: IGNITE-9389 Avoid deadlocks on cache#close()

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4626 ---

Re: Exchange stucks while node restoring state from WAL

Hello Maxim, I think you're going in the right direction, but why you perform binary recovery only in the case when a node in the baseline? I think that node can also perform binary recovery before the first exchange is started in case of 1) First activation 2) Baseline change In all of these cas

[jira] [Created] (IGNITE-9400) TC bot: add progress bar to history page

Ilya Lantukh created IGNITE-9400: Summary: TC bot: add progress bar to history page Key: IGNITE-9400 URL: https://issues.apache.org/jira/browse/IGNITE-9400 Project: Ignite Issue Type: Improve

[jira] [Created] (IGNITE-9401) Newly added testRollbackOnTopologyLockPessimistic has a race which leads to suite hang.

Alexei Scherbakov created IGNITE-9401: - Summary: Newly added testRollbackOnTopologyLockPessimistic has a race which leads to suite hang. Key: IGNITE-9401 URL: https://issues.apache.org/jira/browse/IGNITE-9401

[jira] [Created] (IGNITE-9402) IgnitePdsDiskErrorsRecoveringTest.testRecoveringOnWALWritingFail2 because of LogOnly mode

Anton Kalashnikov created IGNITE-9402: - Summary: IgnitePdsDiskErrorsRecoveringTest.testRecoveringOnWALWritingFail2 because of LogOnly mode Key: IGNITE-9402 URL: https://issues.apache.org/jira/browse/IGNITE-94

[GitHub] ignite pull request #4633: IGNITE-9401 Race fix.

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/4633 IGNITE-9401 Race fix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9401 Alternatively you can review and

[GitHub] ignite pull request #4634: IGNITE-8485: force encrypted mode for all caches

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/4634 IGNITE-8485: force encrypted mode for all caches You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite IGNITE-8485-forced Alternati

[GitHub] ignite pull request #4635: IGNITE-9149 Get rid of logging remaining supplier...

GitHub user ololo3000 opened a pull request: https://github.com/apache/ignite/pull/4635 IGNITE-9149 Get rid of logging remaining supplier nodes rebalance time You can merge this pull request into a Git repository by running: $ git pull https://github.com/ololo3000/ignite IGNIT

Re: Apache Ignite 2.7 release

Hello, Igniters. I think we should discuss the release schedule. Current dates are following: * Code Freeze: September 30, 2018 * Voting Date: October 1, 2018 * Release Date: October 15, 2018 We discussed it privately with Vladimir Ozerov. Is seems better to reschedule

Re: Compression prototype

I have another suggestion which may help us reduce objects size extremely - implementing some kind of SQL Scheme. For now, BinaryObject's format is too excessive - each serialized object stores offset of every serialized field even if the offset can be easily calculated. If we move this metadata

[GitHub] ignite pull request #4633: IGNITE-9401 Race fix.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4633 ---

Re: Compression prototype

Hello! Yes, we can tinker with BinaryObject format, which is currently clearly excessive. But the best part with compression, it will automatically remove this redundancy for us, for free. Even if we had hairy XML as binary object format, it will still compress roughly to the same number of bytes

[GitHub] ignite pull request #4636: IGNITE-9398 Async notification to discovery spi l...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/4636 IGNITE-9398 Async notification to discovery spi listener You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9398 Alt

Re: Apache Ignite 2.7 release

Hi Nikolai, Generally looks OK, however, It is hard to comment on your schedule without seeing a full list of all must-have features we plan to add to this release. I am hoping that the community will see this list at some point. D. On Tue, Aug 28, 2018 at 8:23 AM, Nikolay Izhikov wrote: > Hel

Re: Ignite new contributor

Hello Ravil and welcome to the community! I've added you to the contributor's list in JIRA. Please feel free to take over the tasks. -- Denis On Tue, Aug 28, 2018 at 7:04 AM Ravil Galeyev wrote: > Hi Team, > > I'd like to join to Apache Ignite development. > Especially to the ML part. > Curren

[GitHub] ignite pull request #4637: IGNITE-1678 IgniteAtomicSequence: make following ...

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/4637 IGNITE-1678 IgniteAtomicSequence: make following reservations in advance You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apa

Re: Apache Ignite 2.7 release

Nikolay, Igniters, let me help you with the list. That what I was tracking on my side (something we can announce). Don't have a JIRA ticket for every ticket but CC-ed everyone who claimed to be in charge. Nikolay, please work with the community members to add these capabilities to the release wiki

[GitHub] ignite pull request #4638: Ignite 2.4.8 p3

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

Retries in write-behind store

Folks, Is there a way to limit or disable retries of failed updates in the write-behind store? I can't find one, it looks like if an update fails, it is moved to the end of the queue and then eventually retried. If it fails again, process is repeated. Such behavior *might* be OK if failures are c

Re: Retries in write-behind store

Val, Sounds like a handy configuration option. I would allow setting a number of retries. If the number is set to 0 then a failed update is discarded right away. -- Denis On Tue, Aug 28, 2018 at 9:14 PM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Folks, > > Is there a way to l

[jira] [Created] (IGNITE-9403) TDE - Phase-1. Thin clients

Nikolay Izhikov created IGNITE-9403: --- Summary: TDE - Phase-1. Thin clients Key: IGNITE-9403 URL: https://issues.apache.org/jira/browse/IGNITE-9403 Project: Ignite Issue Type: Sub-task