TisonKun created FLINK-12181:
Summary: Port ExecutionGraphRestartTest to new codebase
Key: FLINK-12181
URL: https://issues.apache.org/jira/browse/FLINK-12181
Project: Flink
Issue Type: Sub-task
TisonKun created FLINK-12179:
Summary: Remove legacy Instance
Key: FLINK-12179
URL: https://issues.apache.org/jira/browse/FLINK-12179
Project: Flink
Issue Type: Sub-task
Components: Run
TisonKun created FLINK-12180:
Summary: Port ExecutionVertexCancelTest to new codebase
Key: FLINK-12180
URL: https://issues.apache.org/jira/browse/FLINK-12180
Project: Flink
Issue Type: Sub-task
TisonKun created FLINK-12178:
Summary: Remove legacy Scheduler
Key: FLINK-12178
URL: https://issues.apache.org/jira/browse/FLINK-12178
Project: Flink
Issue Type: Sub-task
Components: Ru
TisonKun created FLINK-12177:
Summary: Remove legacy FlinkUntypedActor
Key: FLINK-12177
URL: https://issues.apache.org/jira/browse/FLINK-12177
Project: Flink
Issue Type: Sub-task
Compon
TisonKun created FLINK-12176:
Summary: Unify JobGraph creation in CliFrontend
Key: FLINK-12176
URL: https://issues.apache.org/jira/browse/FLINK-12176
Project: Flink
Issue Type: Improvement
Dylan Adams created FLINK-12175:
---
Summary: TypeExtractor.getMapReturnTypes produces different
TypeInformation than createTypeInformation for classes with parameterized
ancestors
Key: FLINK-12175
URL: https://issues
Hello everyone,
@Konstantin Knauf - yes, you are correct.
Between steps 1 and 2 though, the open source organization, in this case
Flink, has to be selected by SoD as one of the participating orgs *fingers
crossed*.
One tip about organizing ideas is that you want to communicate potential
project
Hequn Cheng created FLINK-12174:
---
Summary: Introduce FlinkAggregateExtractProjectRule and remove
extractFieldReferences
Key: FLINK-12174
URL: https://issues.apache.org/jira/browse/FLINK-12174
Project: F
Thanks for sharing the current state of the scheduler refactorings with the
community Gary. The proposed changes look good to me and, hence, +1 for
proceeding with bringing the interfaces into place.
Cheers,
Till
On Fri, Apr 12, 2019 at 5:53 PM Gary Yao wrote:
> Hi all,
>
> As you might have se
Hi all,
As you might have seen already, we are currently reworking Flink's
scheduling.
At the moment, scheduling is a concern that is scattered across different
components, such as ExecutionGraph, Execution and SlotPool. Scheduling also
happens only on the granularity of individual tasks, which ma
Jark Wu created FLINK-12173:
---
Summary: Optimize "SELECT DISTINCT" into Deduplicate with keep
first row
Key: FLINK-12173
URL: https://issues.apache.org/jira/browse/FLINK-12173
Project: Flink
Issue
Hi all,
I read through the SoD documentation again, and now I think, it would
actually make sense to split (1) up into multiple project ideas. Let me
summarize the overall process:
1. We create & publish a list of project ideas, e.g. in a blog post. (This
can be any number of ideas.)
2. Potential
Mario Georgiev created FLINK-12172:
---
Summary: Flink fails to close pending BucketingSink
Key: FLINK-12172
URL: https://issues.apache.org/jira/browse/FLINK-12172
Project: Flink
Issue Type:
Thanks Aljoscha and all for making this happen, I believe 1.8.0 will be a
great and successful release.
Best Regards,
Yu
On Fri, 12 Apr 2019 at 21:23, Patrick Lucas wrote:
> The Docker images for 1.8.0 are now available.
>
> Note that like Flink itself, starting with Flink 1.8 we are no longer
Hello all,
We have deployed the first version of the UI prototype to the following
URL: https://flink-ecosystem-demo.flink-resources.org/#/packages
It has some very basic functionality:
* list packages
* list packages by 'category'
* show a single package
* search that will take you to a search p
The Docker images for 1.8.0 are now available.
Note that like Flink itself, starting with Flink 1.8 we are no longer
providing images with bundled Hadoop. Users who need an image with bundled
Hadoop should create their own, starting from the images published on
Docker Hub and fetching the appropri
Yun Gao created FLINK-12171:
---
Summary: The network buffer memory size should not be checked
against the heap size on the TM side
Key: FLINK-12171
URL: https://issues.apache.org/jira/browse/FLINK-12171
Proje
Hi all,
I'm fine with only preparing the first proposal. I think it's reasonable
because the first proposal is more attractive
and maybe there is not enough Chinese writer. We can focus on one project
to come up with a concrete and
attractive project plan.
One possible subproject could be rework
I am honored to have the opportunity to do a second organization
administrator‘s works!
It seems that one project and multiple projects have their own advantages.
My understanding is that even if we only have one project, we also can have
multiple mentors and recruit enough writers.
Fabian Huesk
Hi all,
thanks Ken & Jark for your comments regarding the Chinese translation
proposal. I seems there is a agreement that project (1) (Improve English
documentation) has a higher priority for us than project (2) (Chinese
translation). We could still write two proposals and indicate priorities
acco
Yes, I think we would get at most one project accepted.
Having all options in a rather generic proposal gives us the most
flexibility to decide what to work on once the proposal is accepted.
On the other hand, a more concrete proposal might look more attractive for
candidates.
I'm fine either way,
I would suggest to make one proposal and have the subsections only in the
project plan.
My understanding is that we need to indicate priorities between proposals
and might get only one, so it would be good to not subdivide.
On Fri, Apr 12, 2019 at 9:58 AM Fabian Hueske wrote:
> Hi everyone,
>
>
godfrey he created FLINK-12170:
--
Summary: Add support for generating optimized logical plan for
Over aggregate
Key: FLINK-12170
URL: https://issues.apache.org/jira/browse/FLINK-12170
Project: Flink
Refer from PR#5185, I think we can use Timebased RocksDBListState to
resolve it.
Timebased RocksDBListState store list entries dispersed in rocksdb like
RocksDBMapState.
Key pair:
For the timebased flink inner class like StreamRecord(enable
event/ingestion time), the rocksdb key is
#KeyGroup#Key#Na
Now that you mentioned configuration, I think the descriptions of the
various configuration options could also be a potential topic. The
descriptions follow very different styles and are often more geared
towards Flink developers than actual users.
On 12/04/2019 09:57, Fabian Hueske wrote:
Hi
Konstantin Knauf created FLINK-12169:
Summary: Improve Javadoc of MessageAcknowledgingSourceBase
Key: FLINK-12169
URL: https://issues.apache.org/jira/browse/FLINK-12169
Project: Flink
Iss
Hi everyone,
I think we can split the first project that Stephan proposed into smaller
ones:
> (1) Create or rework setup / tutorials / concepts docs
> (2) Complete (or advance) the Chinese translation
1.1 Improving (extracting) the documentation of stream processing concepts:
Event-time, Timers
Jingsong Lee created FLINK-12168:
Summary: Support e2e limit, sortLimit, rank, union in blink batch
Key: FLINK-12168
URL: https://issues.apache.org/jira/browse/FLINK-12168
Project: Flink
Issu
29 matches
Mail list logo
