Ray Liu created IGNITE-10818:
Summary: GridQueryTypeDescriptor should have cacheName and alias
field
Key: IGNITE-10818
URL: https://issues.apache.org/jira/browse/IGNITE-10818
Project: Ignite
Sergey Chugunov created IGNITE-10819:
Summary: Test
IgniteClientRejoinTest.testClientsReconnectAfterStart became flaky in master
recently
Key: IGNITE-10819
URL:
Hi Stanislav,
I agree with your suggestions. Taking a step back I realised that, as a
user of an API, I don't want to spend my time refactoring the code due to
API name changes. I need more concrete reasons to do so. I will update the
PR with the required changes, to code and java-docs, for the
Thank you so much Dmitriy, Andrew, Alexey and Anton
Warm Regards,
Saikat
On Tue, Dec 25, 2018 at 10:53 AM Dmitriy Pavlov wrote:
> Hi All,
>
> Please check the commit
>
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=3b9c415ee2c4b6461c18f87f46f1950f324f5662
>
> Thanks to
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Hi All,
Please check the commit
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=3b9c415ee2c4b6461c18f87f46f1950f324f5662
Thanks to everyone involved.
Sincerely,
Dmitriy Pavlov
вт, 25 дек. 2018 г. в 19:38, Dmitriy Pavlov :
> Hi Saikat,
>
> I'm going to slightly change the code
Hi Saikat,
I'm going to slightly change the code before commit.
First of all, I will add more code style and abbreviation rules related
changes.
Second of all, I add pom.xml variables usages where possible.
And last but not least, I'm going to change the implementation of
IgniteSource.
AFAIK
Hello!
I have started reviewing your pull request.
I will expect that scheduled tasks are executed on Public pool. Is it
possible that tasks are launched on Public pool? If Spring Scheduler
insists on its own thread pool, we can have single-thread pool which will
execute put of tasks to public
Vyacheslav Daradur created IGNITE-10817:
---
Summary: Service Grid: Introduce diagnostic tool to dump pending
deployment tasks
Key: IGNITE-10817
URL: https://issues.apache.org/jira/browse/IGNITE-10817
Hi, Sergey!
I think we should keep compatibility as much as possible for Ignite 2.x.
And we can do breaking changes in Ignite 3.x
What do you think?
On Mon, Dec 24, 2018 at 11:58 PM Sergey wrote:
> HI, Igniters!
>
> I've updated and rebased implementation to master branch and made some
>
Andrew Mashenkov created IGNITE-10816:
-
Summary: MVCC: create benchmarks for bulk update operations.
Key: IGNITE-10816
URL: https://issues.apache.org/jira/browse/IGNITE-10816
Project: Ignite
Separate issue has been created to address this: IGNITE-10813.
Best regards,
Andrey Kuznetsov.
пн, 24 дек. 2018, 19:37 dpavlov.ta...@gmail.com:
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
> If your changes can lead to this
Anton Kurbanov created IGNITE-10815:
---
Summary: NullPointerException during
InitNewCoordinatorFuture.init() leads to cluster hang
Key: IGNITE-10815
URL: https://issues.apache.org/jira/browse/IGNITE-10815
Anton Kurbanov created IGNITE-10814:
---
Summary: Exceptions thrown in InitNewCoordinatorFuture.init() are
ignored
Key: IGNITE-10814
URL: https://issues.apache.org/jira/browse/IGNITE-10814
Project:
Andrey Kuznetsov created IGNITE-10813:
-
Summary: Run CheckpointReadLockFailureTest with JUnit4 runner
Key: IGNITE-10813
URL: https://issues.apache.org/jira/browse/IGNITE-10813
Project: Ignite
Hi Andrey,
As far as I know tests annotated by @Ignore can be conveniently tracked on
Teamcity but this requires such tests to be included into JUnit 4 test suite
(org.junit.runners.Suite).
Above requirement currently isn't met by many Ignite tests which are
included in JUnit 3 suites
Vladimir Ozerov created IGNITE-10812:
Summary: SQL: split classes responsible for distributed joins
Key: IGNITE-10812
URL: https://issues.apache.org/jira/browse/IGNITE-10812
Project: Ignite
The test has been fixed within
https://issues.apache.org/jira/browse/IGNITE-10739
Thanks to Oleg Ignatenko!
On Tue, Dec 25, 2018 at 7:37 AM Vyacheslav Daradur wrote:
>
> The failure has been introduced within task:
> https://issues.apache.org/jira/browse/IGNITE-10671 Double
> initialization of
I prepared PR [1] to fix the issue, the test became green.
Anton, could you assist with the merge, please?
[1] https://github.com/apache/ignite/pull/5739
[2] https://ci.ignite.apache.org/viewQueued.html?itemId=2641732
On Tue, Dec 25, 2018 at 10:53 AM Vyacheslav Daradur wrote:
>
> This is my
Dmitry,
As far as I understand, @IgniteIgnore and fail("") works in similar way and
requires test to be muted on TC manually.
And we have to unmute these tests on TC right after fix will be merged to
master, isn't it?
@Ignore and Assume.that works different way comparing to previous two.
Junit
Vyacheslav Daradur created IGNITE-10811:
---
Summary: Add new TC build-config to test Service Grid new and old
implementations
Key: IGNITE-10811
URL: https://issues.apache.org/jira/browse/IGNITE-10811
Anton Dmitriev created IGNITE-10810:
---
Summary: [ML] Import models from MLeap
Key: IGNITE-10810
URL: https://issues.apache.org/jira/browse/IGNITE-10810
Project: Ignite
Issue Type:
22 matches
Mail list logo
