Hi,
if the rest.address is different from the jobmanager.rpc.address, then you
should specify that in the flink-conf.yaml and Flink will connect to
rest.address. Only if rest.address is not specified, the system will fall
back to use the jobmanager.rpc.address. Currently, the rest server endpoint
The Flink project currently receives too many pull requests / has to few
reviewers to ensure timely reviews.
I assume you are talking about https://github.com/apache/flink/pull/5876
If this is correct, something you could already do is squash all commits
and rebase against master to get rid of
Sihua Zhou created FLINK-9633:
-
Summary: Flink doesn't use the Savepoint path's filesystem to
create the OuptutStream on Task.
Key: FLINK-9633
URL: https://issues.apache.org/jira/browse/FLINK-9633
Project
Till Rohrmann created FLINK-9634:
Summary: Deactivate previous location based scheduling if local
recovery is disabled
Key: FLINK-9634
URL: https://issues.apache.org/jira/browse/FLINK-9634
Project: Fl
Till Rohrmann created FLINK-9635:
Summary: Local recovery scheduling can cause spread out of tasks
Key: FLINK-9635
URL: https://issues.apache.org/jira/browse/FLINK-9635
Project: Flink
Issue T
Hi guys,
I have a question. I have been playing around with Fink this week and created
some basic Java jobs that work fine. Now I am trying to run one in Scala.
Running this code in the Scala REP prints the expected output:
env.fromElements(1, 2, 3).map(i => " Integer: " + i).print()
Howev
Hello andrey,
Thanks for the help.
I am trying to implement your above given code code
sourceStream
.setParallelism(4)
.assignTimestampsAndWatermarks(new
BoundedOutOfOrdernessTimestampExtractor<>(…) {…})
.windowAll(TumblingEventTimeWindows.of(Time...))
.p
hi
Yes I've specified the rest.address for the flink client to connect to the
rest.address and the rest.address is valid and working fine but my question
is why am I supposed to give jobmanager.rpc.address for flink client to
connect to flink cluster if flink client depends only on rest.address?
O
The reason why you still have to do it is because we still have to support
the legacy mode where the client needs to know the JobManager RPC address.
Once we remove the legacy mode, we could change the
HighAvailabilityServices such that we have client facing HA services which
only retrieve the rest
Please verify that you have set the correct main class manifest in you
pom.xml when you build the user code jar. Alternatively you can specify the
class to execute via `bin/flink run -c CLASS_TO_EXECUTE` if your user code
jar contains multiple classes.
Cheers,
Till
On Thu, Jun 21, 2018 at 11:28 A
Hi guys,
I am going to answer my own question ;) I looked at a Scala example in the
Flink Github repo, which uses ExecutionEnvironment.getExecutionEnvironment to
obtain the environment. That apparently doesn’t work.
When I change this to StreamExecutionEnvironment.getExecutionEnvironment, as
u
zhijiang created FLINK-9636:
---
Summary: Network buffer leaks in requesting a batch of segments
during canceling
Key: FLINK-9636
URL: https://issues.apache.org/jira/browse/FLINK-9636
Project: Flink
Andrey Zagrebin created FLINK-9637:
--
Summary: Add public user documentation for TTL feature
Key: FLINK-9637
URL: https://issues.apache.org/jira/browse/FLINK-9637
Project: Flink
Issue Type: S
Florian Schmidt created FLINK-9638:
--
Summary: Add helper script to run single e2e test
Key: FLINK-9638
URL: https://issues.apache.org/jira/browse/FLINK-9638
Project: Flink
Issue Type: Improv
Guilherme Nobre created FLINK-9639:
--
Summary: Order "User Configuration" Alphabetically on Flink
Dashboard
Key: FLINK-9639
URL: https://issues.apache.org/jira/browse/FLINK-9639
Project: Flink
Hi,
I've merged the proposed changes for the website.
As usual, we can incrementally refine and improve it.
Best,
Fabian
2018-06-15 16:16 GMT+02:00 Fabian Hueske :
> Hi,
>
> I'm planning to put the reworked website online next week.
> You can have a look at PR #109 [1] to check the changes and
Ok, thanks!
On Thu, Jun 21, 2018, 1:18 AM Chesnay Schepler wrote:
> The Flink project currently receives too many pull requests / has to few
> reviewers to ensure timely reviews.
>
> I assume you are talking about https://github.com/apache/flink/pull/5876
> If this is correct, something you coul
Hai Zhou created FLINK-9640:
---
Summary: Checkpointing is aways aborted if any task has been
finished
Key: FLINK-9640
URL: https://issues.apache.org/jira/browse/FLINK-9640
Project: Flink
Issue Type:
Chris Kellogg created FLINK-9641:
Summary: Pulsar Source Connector
Key: FLINK-9641
URL: https://issues.apache.org/jira/browse/FLINK-9641
Project: Flink
Issue Type: New Feature
Compo
19 matches
Mail list logo
