GitHub user milapfk opened a pull request:
https://github.com/apache/ignite/pull/871
IGNITE-2527 - fixed
Issue:
Calling {{SchedulerFuture.nextExecutionTime()}} (and probably other
methods) on a completed future leads to this exception:
{noformat}
Exception in thread
Hi
I have raised a PR for the following scope.
As a Flink source => run a continuous query against one or multiple
caches
PR https://github.com/apache/ignite/pull/870
Jira https://issues.apache.org/jira/browse/IGNITE-3303
Please review and share feedback.
Regards
Saikat
On Mon, Apr 4, 2016
GitHub user samaitra opened a pull request:
https://github.com/apache/ignite/pull/870
IGNITE-3303 Apache Flink Integration - Flink source to run a continuous
query against one or multiple caches
Apache Flink integration
+++ Ignite as a bidirectional Connector +++
As a
Alexey K.,
No problem, here it is https://issues.apache.org/jira/browse/IGNITE-3488
Sergi
On Sat, Jul 16, 2016 at 2:00 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Folks,
>
> I created one more ticket related to SQL:
> https://issues.apache.org/jira/browse/IGNITE-3487.
Sergi Vladykin created IGNITE-3488:
--
Summary: Prohibit null as name in all the components (cache name
first of all).
Key: IGNITE-3488
URL: https://issues.apache.org/jira/browse/IGNITE-3488
Project: