Alexey Kuznetsov created IGNITE-3816:
Summary: CacheJdbcPojoStore check for column names should be case
insensitive
Key: IGNITE-3816
URL: https://issues.apache.org/jira/browse/IGNITE-3816
Project:
The Project Management Committee (PMC) for Apache Ignite has asked Saikat
Maitra to become a committer and we are pleased to announce that they have
accepted.
Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should e
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/1016
IGNITE-2881 : SPI queries not working
... fixed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2881
Alternati
Github user AMashenkov closed the pull request at:
https://github.com/apache/ignite/pull/1015
---
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 user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/1015
IGNITE-2881 SPI queries not working
... fixed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2881
Alternative
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/1014
IGNITE-3628: Added fetch page size to configuration params.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3628
Hi community,
I raised a pull request [1] Can you please review it?
[1] https://github.com/apache/ignite/pull/1011
Thanks.
Alexey Kuznetsov created IGNITE-3815:
Summary: CacheJdbcPojoStore.loadCache() should check arguments and
fail with appropriate exception message
Key: IGNITE-3815
URL: https://issues.apache.org/jira/browse/IGNI
Ilya Suntsov created IGNITE-3814:
Summary: Unstable results of compute benchmarks
Key: IGNITE-3814
URL: https://issues.apache.org/jira/browse/IGNITE-3814
Project: Ignite
Issue Type: Bug
A
You can shutdown and then restart (after some sleep) network stack on the
host. I remember doing that on Fedora several years ago for exactly the
same purposes.
--Yakov
2016-08-31 15:21 GMT+03:00 Alexey Goncharuk :
> Hi,
>
> As a starting point you can take a look
> at org.apache.ignite.spi.di
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/1012
---
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 en
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/1013
IGNITE-3646 IGFS: Local secondary: Support symlinks for mkdirs operation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apa
Dmitry Karachentsev created IGNITE-3813:
---
Summary: High contention on GridCacheMapEntry.obsolete() on
loading data to data stremer with composite keys
Key: IGNITE-3813
URL: https://issues.apache.org/jira/bro
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/1012
IGNITE-3390: Added DSN configuration window.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3390
Alternatively
Hi,
As a starting point you can take a look
at org.apache.ignite.spi.discovery.tcp.ServerImpl#forceNextNodeFailure
which forces DiscoverySpi to drop next node from the topology (not sure if
this is what you need). Another idea is to create a test discovery SPI
which will terminate all it's threads
Andrew Mashenkov created IGNITE-3812:
Summary: Add executors configuration validation.
Key: IGNITE-3812
URL: https://issues.apache.org/jira/browse/IGNITE-3812
Project: Ignite
Issue Type:
16 matches
Mail list logo