Gary Yao created FLINK-8754:
---
Summary: TaskManagerInfo is not serializable
Key: FLINK-8754
URL: https://issues.apache.org/jira/browse/FLINK-8754
Project: Flink
Issue Type: Bug
Components:
Sihua Zhou created FLINK-8753:
-
Summary: Introduce Incremental savepoint
Key: FLINK-8753
URL: https://issues.apache.org/jira/browse/FLINK-8753
Project: Flink
Issue Type: New Feature
Com
Is the `flink-connector-filesystem` connector supposed to work with the
latest hadoop-free Flink releases, say along with the `flink-s3-fs-presto`
filesystem implementation?
-Jamie
Elias Levy created FLINK-8752:
-
Summary: ClassNotFoundException when using the user code class
loader
Key: FLINK-8752
URL: https://issues.apache.org/jira/browse/FLINK-8752
Project: Flink
Issue T
Elias Levy created FLINK-8751:
-
Summary: Canceling a job results in a InterruptedException in the
JM
Key: FLINK-8751
URL: https://issues.apache.org/jira/browse/FLINK-8751
Project: Flink
Issue Ty
Hi,
I think one improvement that could be made to avoid this situation is the
broadcast state should probably not be rebroadcasted if it was not read.
The problem here is that our program logic ensures that this growing of
state does not occur when it accesses the state, but since we dont to that
Nico Kruber created FLINK-8750:
--
Summary: InputGate may contain data after an EndOfPartitionEvent
Key: FLINK-8750
URL: https://issues.apache.org/jira/browse/FLINK-8750
Project: Flink
Issue Type:
Hey, I am new to flink and I have a question and want to see if anyone can
help here.
How to use Dimension table in Flink TableAPI with StreamExecutionEnvironment ?
I use TableFuncion to deal this question, but it have some problem in debug
like this:
LogicalProject(col_1=[$0])
LogicalJoin(con
Till Rohrmann created FLINK-8749:
Summary: Release slots when scheduling operation is canceled in
ExecutionGraph
Key: FLINK-8749
URL: https://issues.apache.org/jira/browse/FLINK-8749
Project: Flink
Till Rohrmann created FLINK-8748:
Summary: Cancel slot requests for alternatively completed slots in
SlotPool
Key: FLINK-8748
URL: https://issues.apache.org/jira/browse/FLINK-8748
Project: Flink
zhijiang created FLINK-8747:
---
Summary: The tag of waiting for floating buffers in
RemoteInputChannel should be updated properly
Key: FLINK-8747
URL: https://issues.apache.org/jira/browse/FLINK-8747
Project:
Till Rohrmann created FLINK-8746:
Summary: Support rescaling of jobs which are not fully running
Key: FLINK-8746
URL: https://issues.apache.org/jira/browse/FLINK-8746
Project: Flink
Issue Typ
Right now, I don’t think there is a way of doing that. I don’t think there is
something fundament against having a method that drops a state complete, data
and registered meta data. But so far that never existed and it seems nobody
ever needed it (or asked for it at least). The closest thing for
I had a quick look at it, and we could do that, even for RocksDB: the method
does a meta data lookup similar to what state registration does, remove the
meta data and drop the column family. But until then, there is currently no
complete dropping a keyed state.
> Am 22.02.2018 um 12:19 schrieb
Chesnay Schepler created FLINK-8745:
---
Summary: Reduce travis usage
Key: FLINK-8745
URL: https://issues.apache.org/jira/browse/FLINK-8745
Project: Flink
Issue Type: Improvement
Com
Do you have any suggestion how to completely delete an operator and keyed
state?
For operator state this seems to be easy enough, but what about completely
dropping a keyed state?
Gyula
Stefan Richter ezt írta (időpont: 2018. febr.
22., Cs, 11:46):
>
> Hi,
>
> I don’t think that this is a bug,
Hi,
I don’t think that this is a bug, but rather a necessity that comes with the
(imo questionable) design of allowing lazy state registration. In this design,
just because a state is *currently* not registered does not mean that you can
simply drop it. Imagine that your code did *not yet* re-
They reason they didn't catch this is that the bug only occurs if users use a
custom timestamp/watermark assigner. But yes, we should be able to extend the
end-to-end tests to catch this.
> On 22. Feb 2018, at 11:05, Till Rohrmann wrote:
>
> If the Kafka connectors are unusable with 1.4.1, the
While we're on this:
https://beam.apache.org/blog/2017/08/16/splittable-do-fn.html
This is a concrete way of separating partition/shard/split discovery from their
reading. The nice thing about this is that you can mix-and-match "discovery
components" and "reader components". For example, for Ka
+1
> On 22. Feb 2018, at 11:13, Till Rohrmann wrote:
>
> +1
>
> Cheers,
> Till
>
> On Wed, Feb 21, 2018 at 11:40 PM, Bowen Li wrote:
>
>> +1.
>>
>> flink-contrib is an experiment land, docker-flink should graduate from it.
>> This also helps to clean up flink-contrib/
>>
>>
>>
>> On Wed,
+1
Cheers,
Till
On Wed, Feb 21, 2018 at 11:40 PM, Bowen Li wrote:
> +1.
>
> flink-contrib is an experiment land, docker-flink should graduate from it.
> This also helps to clean up flink-contrib/
>
>
>
> On Wed, Feb 21, 2018 at 1:41 PM, Stephan Ewen wrote:
>
> > Hi all!
> >
> > I want to start
Hi all,
We have discovered a fairly serious memory leak
in DefaultOperatorStateBackend, with broadcast (union) list states.
The problem seems to occur when a broadcast state name is changed, in order
to drop some state (intentionally).
Flink does not drop the "garbage" broadcast state, and keeps
If the Kafka connectors are unusable with 1.4.1, then I would be in favor
of releasing 1.4.2 asap.
I'm wondering why the end-to-end Kafka tests did not catch this problem.
Maybe we could adapt them such that they guard against it in the future.
Cheers,
Till
On Thu, Feb 22, 2018 at 9:46 AM, Tzu-L
Chesnay Schepler created FLINK-8744:
---
Summary: Add annotations for documentation common/advanced options
Key: FLINK-8744
URL: https://issues.apache.org/jira/browse/FLINK-8744
Project: Flink
Chesnay Schepler created FLINK-8743:
---
Summary: Add annotation to override documented default
Key: FLINK-8743
URL: https://issues.apache.org/jira/browse/FLINK-8743
Project: Flink
Issue Type:
Chesnay Schepler created FLINK-8742:
---
Summary: Move ConfigDocsGenerator annotationt to flink-annotations
Key: FLINK-8742
URL: https://issues.apache.org/jira/browse/FLINK-8742
Project: Flink
Hi all,
Unfortunately, we've discovered a bug in 1.4.1, which suggests that we
should almost immediately release another bugfix release:
https://issues.apache.org/jira/browse/FLINK-8741.
Since this issue was introduced only in 1.4.1, it might make sense to
release 1.4.2 with only the fix for FLIN
Tzu-Li (Gordon) Tai created FLINK-8741:
--
Summary: KafkaFetcher09/010/011 uses wrong user code classloader
Key: FLINK-8741
URL: https://issues.apache.org/jira/browse/FLINK-8741
Project: Flink
28 matches
Mail list logo
