[GitHub] ignite pull request: IGNITE-2899 BinaryObject is deserialized befo...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/593 --- 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: IGNITE-3182 Compute jobs execute on client no...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/748 IGNITE-3182 Compute jobs execute on client nodes You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-3182 Alternatively

[jira] [Created] (IGNITE-3186) [Test] org.apache.ignite.internal.processors.igfs.IgfsProcessorValidationSelfTest#testInvalidEndpointTcpPort fails on master

Ivan Veselovsky created IGNITE-3186: --- Summary: [Test] org.apache.ignite.internal.processors.igfs.IgfsProcessorValidationSelfTest#testInvalidEndpointTcpPort fails on master Key: IGNITE-3186 URL:

[jira] [Created] (IGNITE-3185) Hadoop: Improve Hadoop JAR search logic.

Vladimir Ozerov created IGNITE-3185: --- Summary: Hadoop: Improve Hadoop JAR search logic. Key: IGNITE-3185 URL: https://issues.apache.org/jira/browse/IGNITE-3185 Project: Ignite Issue Type:

Implementing Decimals for C++

Hi Igniters, Currently, I'm working on implementation of analogue of BigDecimal for C++ so that we would be able to support SQL_NUMERIC type for ODBC [1]. I've taken implementation of the BigDecimal class in Java as the base for the C++ implementation. Now I'm wondering, could we have any legal

[jira] [Created] (IGNITE-3184) Hadoop: HADOOP_HOME should not be required if all other environment variables are set.

Vladimir Ozerov created IGNITE-3184: --- Summary: Hadoop: HADOOP_HOME should not be required if all other environment variables are set. Key: IGNITE-3184 URL: https://issues.apache.org/jira/browse/IGNITE-3184

[GitHub] ignite pull request: 7.5.23

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

[GitHub] ignite pull request: IGNITE-2744 : unwindEvicts() usage optimizati...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/647 --- 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: IGNITE-1690 testing.

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

[jira] [Created] (IGNITE-3183) ScanQuery and localEntries are ignored keepBinary flag in OFFHEAP_TIERED mode

Nikolay Tikhonov created IGNITE-3183: Summary: ScanQuery and localEntries are ignored keepBinary flag in OFFHEAP_TIERED mode Key: IGNITE-3183 URL: https://issues.apache.org/jira/browse/IGNITE-3183

Re: Deadlock detection usage

Dmitry, In this case "blocked" means that transaction can't be rolled back while deadlock detection isn't completed. As soon as detection completes transaction can be rolled back and, for example, retried. So in cases when deadlock detection is switched off transactions will be just rolled back

[GitHub] ignite pull request: IGNITE-2865 Continuous query event passed to ...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/744 IGNITE-2865 Continuous query event passed to filter should be immutale for users. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request: IGNITE-2865 Continuous query event passed to ...

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

[jira] [Created] (IGNITE-3182) Compute jobs execute on client nodes

Pavel Tupitsyn created IGNITE-3182: -- Summary: Compute jobs execute on client nodes Key: IGNITE-3182 URL: https://issues.apache.org/jira/browse/IGNITE-3182 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request: Ignite 3164

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

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

Ignite 1.6.0 successfuly released to https://dist.apache.org/repos/dist/release/ignite/1.6.0/ Maven repository and site also updated. On Sat, May 21, 2016 at 6:47 PM, Anton Vinogradov wrote: > Hello! > > Apache Ignite 1.6.0 release (RC1) has been accepted. > > 9 "+1" votes

[GitHub] ignite pull request: IGNITE-3175 BigDecimal fields are not support...

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

[GitHub] ignite pull request: ignite-2528

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