Folks,
Recently I have seen a couple of emails suggesting tasks/improvements that
we cannot do in 1.x releases due to API compatibility reasons, so they are
postponed to 2.0. I would like to keep track of these tasks in some way in
our Jira to make sure we do not have anything obsolete when it com
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/817
---
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
Hi,
As Andrey pointed out, now you can grab an expiry policy factory from
Ignite's cache configuration, create an instance and get durations you
need. I agree that this way a bit awkward and it only covers a configured
ExpiryPolicy, currently there is no way to check if an instance of
IgniteCache
Pavel Tupitsyn created IGNITE-3368:
--
Summary: .NET: Improve test coverage
Key: IGNITE-3368
URL: https://issues.apache.org/jira/browse/IGNITE-3368
Project: Ignite
Issue Type: Task
C
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/826
---
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
Vladimir Ozerov created IGNITE-3367:
---
Summary: Hadoop: increase protocol client idle timeout.
Key: IGNITE-3367
URL: https://issues.apache.org/jira/browse/IGNITE-3367
Project: Ignite
Issue T
Vladimir Ozerov created IGNITE-3366:
---
Summary: Hadoop: Improve configuration defaults.
Key: IGNITE-3366
URL: https://issues.apache.org/jira/browse/IGNITE-3366
Project: Ignite
Issue Type: Ta
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/830
---
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/830
IGNITE-3364 .NET: Fix BinaryReflectiveSerializer raw mode for DateTime
members marked with QuerySqlField
You can merge this pull request into a Git repository by running:
$ git pull https:/
Pavel Tupitsyn created IGNITE-3365:
--
Summary: .NET: User-defined affinity mapper
Key: IGNITE-3365
URL: https://issues.apache.org/jira/browse/IGNITE-3365
Project: Ignite
Issue Type: New Featu
Pavel Tupitsyn created IGNITE-3364:
--
Summary: .NET: BinaryReflectiveSerializer raw mode does not work
with DateTime fields
Key: IGNITE-3364
URL: https://issues.apache.org/jira/browse/IGNITE-3364
Proj
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/829
IGNITE-3140: Added tests for string format validity.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/isapego/ignite ignite-3140
Alternatively y
Pavel Tupitsyn created IGNITE-3363:
--
Summary: Forward Java output to the .NET console
Key: IGNITE-3363
URL: https://issues.apache.org/jira/browse/IGNITE-3363
Project: Ignite
Issue Type: New
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/828
IGNITE-3362
Unit test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vldpyatkov/ignite ignite-3362
Alternatively you can review and apply th
Vladislav Pyatkov created IGNITE-3362:
-
Summary: Event EVT_CACHE_REBALANCE_STOPPED fires prematurely.
Key: IGNITE-3362
URL: https://issues.apache.org/jira/browse/IGNITE-3362
Project: Ignite
15 matches
Mail list logo