Vladimir Ozerov created IGNITE-3187:
---
Summary: IGFS: Print acceptable IGFS endpoints to the console on
node start.
Key: IGNITE-3187
URL: https://issues.apache.org/jira/browse/IGNITE-3187
Project: Ig
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/749
Ignite 2969
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-2969
Alternatively you can review and apply these chang
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 enab
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 y
Ivan Veselovsky created IGNITE-3186:
---
Summary: [Test]
org.apache.ignite.internal.processors.igfs.IgfsProcessorValidationSelfTest#testInvalidEndpointTcpPort
fails on master
Key: IGNITE-3186
URL: https://issues.a
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: B
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 (
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 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 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 enab
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
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
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/745
IGNITE-2888
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ilantukh/ignite ignite-2888
Alternatively you can review and apply these changes a
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 i
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 https://github.com/grid
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 featu
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 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 c
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 received.
>
> Here are
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/742
IGNITE-2865 Continuous query event passed to filter should be immutable for
users.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gri
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 featu
21 matches
Mail list logo
