Yujue Li created IGNITE-5696:
Summary: A localListenAsync method is missing in the
IgniteMessaging interface.
Key: IGNITE-5696
URL: https://issues.apache.org/jira/browse/IGNITE-5696
Project: Ignite
GitHub user samaitra opened a pull request:
https://github.com/apache/ignite/pull/2241
IGNITE-5695 FlinkIgniteSinkSelfTest is failing due to conflicting defâ¦
â¦ault test timeout and default flush frequency
You can merge this pull request into a Git repository by running:
$
Saikat Maitra created IGNITE-5695:
-
Summary: FlinkIgniteSinkSelfTest is failing due to conflicting
default test timeout and default flush frequency
Key: IGNITE-5695
URL:
Github user samaitra closed the pull request at:
https://github.com/apache/ignite/pull/887
---
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 samaitra closed the pull request at:
https://github.com/apache/ignite/pull/926
---
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 samaitra closed the pull request at:
https://github.com/apache/ignite/pull/847
---
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 samaitra closed the pull request at:
https://github.com/apache/ignite/pull/392
---
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
Yakov,
Since you filed this ticket, can you please comment?
D.
On Tue, Jul 4, 2017 at 6:47 AM, Vitaliy Biryukov <
biryukovvitali...@gmail.com> wrote:
> Andrew Mashenkov wrote
> > Thus,
> > *there will no need to pass cache context to methods and classes
> > increasing
> > code complexity.
> >
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/2240
ignite-5694 : Retries for getCollection().
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5694
Alternatively
Ilya Lantukh created IGNITE-5694:
Summary:
IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover()
fails sometimes
Key: IGNITE-5694
URL: https://issues.apache.org/jira/browse/IGNITE-5694
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/2239
ignite-5693 : Fixed flaky test.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5693
Alternatively you can
Github user ilantukh closed the pull request at:
https://github.com/apache/ignite/pull/2238
---
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 ilantukh opened a pull request:
https://github.com/apache/ignite/pull/2238
ignite-5693
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5693
Alternatively you can review and apply these
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/2237
IGNITE-5663: ODBC: Closing cursor do not reset prepared statement anymore
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/2236
test-PR-ignite-5097
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Sberbank-Technology/ignite ignite-5097
Alternatively you can review and
Hi, Val,
No, this plugin is not available in apache-ignite code base.
May be we should remove reference from JIRA or add this plugin (and also
other code inspections) into AI code base.
Thoughts?
Sincerely,
Dmitriy Pavlov
вт, 4 июл. 2017 г. в 1:29, Valentin Kulichenko <
Igniters,
We have 536 tickets assinged to 2.1 release [1]. I propose to move all the
tickets which will not be ready by the end of the week to the next release.
You may use this report [2], which will show all the issues which are
either reported by you or assigned to you (you must be logged in
Pavel Kovalenko created IGNITE-5692:
---
Summary: IgnitePdsCacheRebalancingAbstractTest suite hangs on TC
Key: IGNITE-5692
URL: https://issues.apache.org/jira/browse/IGNITE-5692
Project: Ignite
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/2235
two tests unmuted, one test removed as obsolete (IGNITE-5592)
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/2234
IGNITE-5482
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5482-merge
Alternatively you can review and
Github user alexpaschenko closed the pull request at:
https://github.com/apache/ignite/pull/2139
---
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
Ilya Lantukh created IGNITE-5690:
Summary: JavaEmbeddedIgniteRDDSelfTest sometimes hangs on TC
Key: IGNITE-5690
URL: https://issues.apache.org/jira/browse/IGNITE-5690
Project: Ignite
Issue
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/2233
IGNITE-5679: add JDBC example
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5679
Alternatively you
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/2232
---
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 user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/2232
IGNITE-5679 JDBC thin driver: add example
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.1.2
Ilya Lantukh created IGNITE-5689:
Summary: IgniteCommunicationBalanceTest hangs on Windows
Key: IGNITE-5689
URL: https://issues.apache.org/jira/browse/IGNITE-5689
Project: Ignite
Issue Type:
Artem Malykh created IGNITE-5688:
Summary: Fix SparseDistributedMatrixTest::testCacheBehaviour crash
Key: IGNITE-5688
URL: https://issues.apache.org/jira/browse/IGNITE-5688
Project: Ignite
As it is explicitly stated in Javadoc of PluginProvider#onIgniteStart
that all internal components should be started before this method is
called, which is not true, as internal component callbacks are called
right after the PluginProvider#onIgniteStart.
On 7/2/2017 12:58 PM, Evgeniy Ignatiev
Andrew Mashenkov wrote
> Thus,
> *there will no need to pass cache context to methods and classes
> increasing
> code complexity.
> *end user will have ability to tune every single query.
> *avoid confusing situation with running same query on different caches.
To satisfy all these points, I need
Pavel Tupitsyn created IGNITE-5687:
--
Summary: .NET: Store deserialized values on heap optionally
Key: IGNITE-5687
URL: https://issues.apache.org/jira/browse/IGNITE-5687
Project: Ignite
Guys,
We have a ticket that is implemented, but the ticket itseft and the
solution looks confusing as ticket title is differs to its description:
"IGNITE-5468: Need to set IGNITE_SQL_MERGE_TABLE_MAX_SIZE on per query
basis" [1]
Seems, initially, we want to have ability to change these 2
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/2231
IGNITE-GG-11209 Extract File I/O interface
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-11209
Alexey Goncharuk created IGNITE-5686:
Summary: Endless partition eviction during node shutdown
Key: IGNITE-5686
URL: https://issues.apache.org/jira/browse/IGNITE-5686
Project: Ignite
Igniters,
Persistent store has been merged to master branch! "master-bak" branch was
created to keep the state before merge for safety. As release date for 2.1
is mid July, I created "ignite-2.1" branch where we will stabilize the
release as usual. Please push features and fixes planned for 2.1
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2029
---
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 asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2157
---
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 asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2145
---
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 asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2169
---
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 asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2156
---
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 asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2152
---
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 asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2135
---
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 asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2002
---
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 asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2171
---
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 asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1821
---
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 asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2120
---
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 asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1924
---
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 asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1864
---
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 asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1859
---
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
Andrey Gura created IGNITE-5685:
---
Summary: JDBC: Prepared statement shouldn't clear params after
query execution
Key: IGNITE-5685
URL: https://issues.apache.org/jira/browse/IGNITE-5685
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1842
---
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 mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/2230
IGNITE-5554 ServiceProcessor may process failed reassignments in timeout
thread
You can merge this pull request into a Git repository by running:
$ git pull
Vladimir Ozerov created IGNITE-5684:
---
Summary:
IgniteClientCacheStartFailoverTest.testClientStartLastServerFails* fails
Key: IGNITE-5684
URL: https://issues.apache.org/jira/browse/IGNITE-5684
Alexey Kuznetsov created IGNITE-5683:
Summary: Web Console: missing fully qualified name for generated
indexed types on Models Screen
Key: IGNITE-5683
URL: https://issues.apache.org/jira/browse/IGNITE-5683
Vladimir Ozerov created IGNITE-5682:
---
Summary: GridCacheRabalancingDelayedPartitionMapExchangeSelfTest
fails
Key: IGNITE-5682
URL: https://issues.apache.org/jira/browse/IGNITE-5682
Project: Ignite
Vladimir Ozerov created IGNITE-5681:
---
Summary:
IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover
fails
Key: IGNITE-5681
URL: https://issues.apache.org/jira/browse/IGNITE-5681
Vladimir Ozerov created IGNITE-5679:
---
Summary: JDBC thin driver: add example
Key: IGNITE-5679
URL: https://issues.apache.org/jira/browse/IGNITE-5679
Project: Ignite
Issue Type: Task
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/2229
IGNITE-GG-12418 Fix hanging WAL flusher
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12418-fix
57 matches
Mail list logo
