Bowen Li created FLINK-7660:
---
Summary: Support sideOutput in ProcessAllWindowFunction
Key: FLINK-7660
URL: https://issues.apache.org/jira/browse/FLINK-7660
Project: Flink
Issue Type: Improvement
Ted Yu created FLINK-7659:
-
Summary: Unprotected access to inProgress in
JobCancellationWithSavepointHandlers#handleNewRequest
Key: FLINK-7659
URL: https://issues.apache.org/jira/browse/FLINK-7659
Project: Fl
Shuyi Chen created FLINK-7658:
-
Summary: Support COLLECT Aggregate function in Flink TABLE API
Key: FLINK-7658
URL: https://issues.apache.org/jira/browse/FLINK-7658
Project: Flink
Issue Type: New
Hi Federico,
As far as I know, the Kafka client code has been rewritten in Java for version
0.9, meaning there is no more Scala dependency in there. Only the server
(broker) code still contains Scala but it doesn't matter what Scala version a
client uses, if any.
Best,
Aljoscha
> On 20. Sep 2
Kent Murra created FLINK-7657:
-
Summary: SQL Timestamps Converted To Wrong Type By Optimizer
Causing ClassCastException
Key: FLINK-7657
URL: https://issues.apache.org/jira/browse/FLINK-7657
Project: Flink
+ 1
> On Sep 20, 2017, at 2:26 PM, Stefan Richter
> wrote:
>
> +1
Fabian Hueske created FLINK-7656:
Summary: Switch to user ClassLoader when invoking
initializeOnMaster finalizeOnMaster
Key: FLINK-7656
URL: https://issues.apache.org/jira/browse/FLINK-7656
Project: F
Hi, as far as I know some vendors like Hortonworks still use Kafka_2.10 as
part of their hadoop distribution.
Could the use of a different scala version cause issues with the Kafka
connector? I'm asking because we are using HDP 2.6 and we once already had
some issue with conflicting scala versions
Till Rohrmann created FLINK-7655:
Summary: Revisit default non-leader id for FencedRpcEndpoints
Key: FLINK-7655
URL: https://issues.apache.org/jira/browse/FLINK-7655
Project: Flink
Issue Type
+1
2017-09-20 14:30 GMT+02:00 Kostas Kloudas :
> +1
>
> > On Sep 20, 2017, at 2:26 PM, Stefan Richter
> wrote:
> >
> > +1
>
>
+1
> On Sep 20, 2017, at 2:26 PM, Stefan Richter
> wrote:
>
> +1
+1
+1
Original message From: Hai Zhou Date:
9/20/17 12:44 AM (GMT-08:00) To: Aljoscha Krettek ,
dev@flink.apache.org, user Subject: Re: [DISCUSS]
Dropping Scala 2.10
+1
> 在 2017年9月19日,17:56,Aljoscha Krettek 写道:
>
> Hi,
>
> Talking to some people I get the impression that S
Hai Zhou_UTC+8 created FLINK-7654:
-
Summary: Update RabbitMQ Java client to 4.x
Key: FLINK-7654
URL: https://issues.apache.org/jira/browse/FLINK-7654
Project: Flink
Issue Type: Improvement
Tzu-Li (Gordon) Tai created FLINK-7653:
--
Summary: Properly implement DispatcherGateway methods on the
Dispatcher
Key: FLINK-7653
URL: https://issues.apache.org/jira/browse/FLINK-7653
Project: Fli
Tzu-Li (Gordon) Tai created FLINK-7652:
--
Summary: Port CurrentJobIdsHandler to new REST endpoint
Key: FLINK-7652
URL: https://issues.apache.org/jira/browse/FLINK-7652
Project: Flink
Issu
Tzu-Li (Gordon) Tai created FLINK-7650:
--
Summary: Port JobCancellationHandler to new REST endpoint
Key: FLINK-7650
URL: https://issues.apache.org/jira/browse/FLINK-7650
Project: Flink
Is
Till Rohrmann created FLINK-7651:
Summary: RetryingRegistration does not wait between failed
connection attempts
Key: FLINK-7651
URL: https://issues.apache.org/jira/browse/FLINK-7651
Project: Flink
Tzu-Li (Gordon) Tai created FLINK-7649:
--
Summary: Port JobStoppingHandler to new REST endpoint
Key: FLINK-7649
URL: https://issues.apache.org/jira/browse/FLINK-7649
Project: Flink
Issue
Tzu-Li (Gordon) Tai created FLINK-7648:
--
Summary: Port TaskManagersHandler to new REST endpoint
Key: FLINK-7648
URL: https://issues.apache.org/jira/browse/FLINK-7648
Project: Flink
Issue
Tzu-Li (Gordon) Tai created FLINK-7647:
--
Summary: Port JobManagerConfigHandler to new REST endpoint
Key: FLINK-7647
URL: https://issues.apache.org/jira/browse/FLINK-7647
Project: Flink
I
+1
> 在 2017年9月19日,17:56,Aljoscha Krettek 写道:
>
> Hi,
>
> Talking to some people I get the impression that Scala 2.10 is quite outdated
> by now. I would like to drop support for Scala 2.10 and my main motivation is
> that this would allow us to drop our custom Flakka build of Akka that we use
Hi XiangWei,
programmatically there is no nice tooling yet to cancel jobs on a dedicated
cluster. What you can do is to use Flink's REST API to issue a cancel
command [1]. You have to send a GET request to the target URL
`/jobs/:jobid/cancel`. In the future we will improve the programmatic job
con
23 matches
Mail list logo