Nikolay Izhikov created IGNITE-12286:
Summary: NPE in SQLView exporter when filter is null
Key: IGNITE-12286
URL: https://issues.apache.org/jira/browse/IGNITE-12286
Project: Ignite
Issue
Ilya,
I agree that issues related to `documentation` can be safely
postponed, however, for me the whole batch of such issues looks
unmanageable and unclear. At least we should prioritize all of them to
complete the maximum that we can by the deadline.
On Thu, 10 Oct 2019 at 19:47, Ilya Kasnacheev
Maxim Muzafarov created IGNITE-12287:
Summary: Checkstyle violation unused imports
JavaEmbeddedIgniteRDDWithLocalStoreSelfTest
Key: IGNITE-12287
URL: https://issues.apache.org/jira/browse/IGNITE-12287
Igniters,
The `checkstyle` profile has been enabled for the Apache Ignite build procedure.
Unused imports in the spark module have been fixed [1].
The `[Check Code Style]` suite has been excluded from `Run :: All`,
`Run :: ML`.
[1] https://issues.apache.org/jira/browse/IGNITE-12287
On Tue, 8 Oct
Please, return checkstyle to run Ml, I use this feature
вс, 13 окт. 2019 г., 18:52 Maxim Muzafarov :
> Igniters,
>
> The `checkstyle` profile has been enabled for the Apache Ignite build
> procedure.
> Unused imports in the spark module have been fixed [1].
> The `[Check Code Style]` suite has be
Hi @Saikat Maitra
I have my implementation on an Ignite fork on my personal GitHub account [1]
It is based on the Kafka implementation which is of a polling nature.
GCP does not provide a service like Kafka. Instead it provides us with
Pub/Sub which is just like Kafka.
Therefore using the Kafka st
Folks,
We should avoid heavy merges if possible.
I'm ok with IEP to keep tasks properly, but strictly against all-in-one
"+27000,-18200" merges.
This task implements Sandbox (API + core) which covered by tests and by
some integrations with existing components, which is enough to merge.
The most im
