[
https://issues.apache.org/jira/browse/FLINK-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing reassigned FLINK-4348:
Assignee: zhangjing
> implement communication from ResourceManager to TaskManager
>
zhangjing created FLINK-4353:
Summary: cluster components failure process
Key: FLINK-4353
URL: https://issues.apache.org/jira/browse/FLINK-4353
Project: Flink
Issue Type: Sub-task
zhangjing created FLINK-4350:
Summary: ResourceManager interaction
Key: FLINK-4350
URL: https://issues.apache.org/jira/browse/FLINK-4350
Project: Flink
Issue Type: Sub-task
Components:
zhangjing created FLINK-4351:
Summary: TaskExecutor interaction
Key: FLINK-4351
URL: https://issues.apache.org/jira/browse/FLINK-4351
Project: Flink
Issue Type: Sub-task
Components:
zhangjing created FLINK-4349:
Summary: ResourceManager interaction
Key: FLINK-4349
URL: https://issues.apache.org/jira/browse/FLINK-4349
Project: Flink
Issue Type: Task
Reporter:
[
https://issues.apache.org/jira/browse/FLINK-4349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing closed FLINK-4349.
Resolution: Invalid
> ResourceManager interaction
> ---
>
> Key:
[
https://issues.apache.org/jira/browse/FLINK-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4350:
-
Description:
1. Send Slot Request to ResourceManager
2. Cancel SlotRequest to ResourceManager
3. Register
zhangjing created FLINK-4352:
Summary: JobClient interaction
Key: FLINK-4352
URL: https://issues.apache.org/jira/browse/FLINK-4352
Project: Flink
Issue Type: Sub-task
Components:
zhangjing created FLINK-4356:
Summary: JobMaster HA
Key: FLINK-4356
URL: https://issues.apache.org/jira/browse/FLINK-4356
Project: Flink
Issue Type: Sub-task
Reporter: zhangjing
1.
[
https://issues.apache.org/jira/browse/FLINK-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4351:
-
Summary: interaction between new JobManager and new TaskManager (was:
TaskExecutor interaction)
>
[
https://issues.apache.org/jira/browse/FLINK-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4352:
-
Summary: interaction between new JobManager and JobClient (was: JobClient
interaction)
> interaction
[
https://issues.apache.org/jira/browse/FLINK-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4356:
-
Summary: new JobManager HA (was: JobMaster HA)
> new JobManager HA
> -
>
>
[
https://issues.apache.org/jira/browse/FLINK-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4350:
-
Summary: interaction between new JobMaster and new ResourceManager (was:
ResourceManager interaction)
>
[
https://issues.apache.org/jira/browse/FLINK-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4350:
-
Summary: interaction between new JobManager and new ResourceManager (was:
interaction between new
[
https://issues.apache.org/jira/browse/FLINK-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4353:
-
Summary: new JobManager handle cluster components failure (was: cluster
components failure process)
>
zhangjing created FLINK-5737:
Summary: Let flink table support byte[] field type
Key: FLINK-5737
URL: https://issues.apache.org/jira/browse/FLINK-5737
Project: Flink
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/FLINK-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-5568:
-
Summary: Introduce interface for catalog, and provide an in-memory
implementation, migrate current table
[
https://issues.apache.org/jira/browse/FLINK-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing resolved FLINK-5569.
--
Resolution: Duplicate
> Migrate current table registration to in-memory catalog
>
[
https://issues.apache.org/jira/browse/FLINK-5737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15864852#comment-15864852
]
zhangjing commented on FLINK-5737:
--
Hi Fabian, thanks a lot. The bug was already fixed, I will close this
[
https://issues.apache.org/jira/browse/FLINK-5737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing closed FLINK-5737.
Resolution: Fixed
> Fix the bug when TableSource contains a field of byte[] type
>
[
https://issues.apache.org/jira/browse/FLINK-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing reassigned FLINK-5570:
Assignee: zhangjing
> Support register external catalog to table environment
>
[
https://issues.apache.org/jira/browse/FLINK-5737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-5737:
-
Description:
At current, if a TableSource contains a field of byte[] type, TableException
would be
[
https://issues.apache.org/jira/browse/FLINK-5737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-5737:
-
Description:
At current, if a TableSource contains a field of byte[] type, TableException
would be
[
https://issues.apache.org/jira/browse/FLINK-5737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-5737:
-
Description: (was: Field type of flink table cannot be byte[]
currently, but it is useful in many
[
https://issues.apache.org/jira/browse/FLINK-5737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-5737:
-
Description:
At current, if a TableSource contains a field of byte[] type, TableException
would be
[
https://issues.apache.org/jira/browse/FLINK-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-5566:
-
Description:
We define two structure mode to hold statistics
1. TableStats: contain stats for table
[
https://issues.apache.org/jira/browse/FLINK-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-5567:
-
Description:
1. Introduce FlinkStatistic class, which is subclass of Calcite Statistic.
2. Integrate
[
https://issues.apache.org/jira/browse/FLINK-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing reassigned FLINK-5568:
Assignee: zhangjing
> Introduce interface for catalog, and provide an in-memory implementation
>
[
https://issues.apache.org/jira/browse/FLINK-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436167#comment-15436167
]
zhangjing commented on FLINK-4478:
--
[~till.rohrmann]. I agree we should define how should it look like
[
https://issues.apache.org/jira/browse/FLINK-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15453902#comment-15453902
]
zhangjing commented on FLINK-4535:
--
Hi, Max, I already saw RetryingRegistration. Now it can only accept
[
https://issues.apache.org/jira/browse/FLINK-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4547:
-
Summary: when call connect method in AkkaRpcService using same address and
same rpc gateway class, the
[
https://issues.apache.org/jira/browse/FLINK-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4348:
-
Description:
When slotManager finds a proper slot in the free pool for a slot request,
slotManager
zhangjing created FLINK-4547:
Summary: Return same object when call connect method in
AkkaRpcService using same address and same rpc gateway class
Key: FLINK-4547
URL: https://issues.apache.org/jira/browse/FLINK-4547
[
https://issues.apache.org/jira/browse/FLINK-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4547:
-
Description:
Now every time call connect method in AkkaRpcService class using same address
and same rpc
[
https://issues.apache.org/jira/browse/FLINK-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing reassigned FLINK-4537:
Assignee: zhangjing
> ResourceManager registration with JobManager
>
[
https://issues.apache.org/jira/browse/FLINK-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4537:
-
Description:
The ResourceManager keeps tracks of all JobManager's which execute Jobs. When a
new
[
https://issues.apache.org/jira/browse/FLINK-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing reassigned FLINK-4547:
Assignee: zhangjing
> Return same object when call connect method in AkkaRpcService using same
>
[
https://issues.apache.org/jira/browse/FLINK-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4449:
-
Description: ResourceManager need two HeartbeatManagers. One for monitor
the connections with all
[
https://issues.apache.org/jira/browse/FLINK-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4449:
-
Description: ResourceManager need a heartbeat manager to monitor the
connections with all registered
[
https://issues.apache.org/jira/browse/FLINK-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4537:
-
Description:
The ResourceManager keeps tracks of all JobManager's which execute Jobs. When a
new
[
https://issues.apache.org/jira/browse/FLINK-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4449:
-
Summary: Heartbeat Manager integration with TaskExecutor (was: Heartbeat
Manager integration with
zhangjing created FLINK-4551:
Summary: Heartbeat Manager integration with JobMaster
Key: FLINK-4551
URL: https://issues.apache.org/jira/browse/FLINK-4551
Project: Flink
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/FLINK-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing reassigned FLINK-4551:
Assignee: zhangjing
> Heartbeat Manager integration with JobMaster
>
[
https://issues.apache.org/jira/browse/FLINK-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4535:
-
Description:
When TaskExecutor register at ResourceManager, it takes the following 3 input
parameter:
1.
[
https://issues.apache.org/jira/browse/FLINK-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4535:
-
Description:
When TaskExecutor register at ResourceManager, it will have the following 3
input
zhangjing created FLINK-4535:
Summary: ResourceManager process registration from TaskExecutor
Key: FLINK-4535
URL: https://issues.apache.org/jira/browse/FLINK-4535
Project: Flink
Issue Type:
[
https://issues.apache.org/jira/browse/FLINK-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4535:
-
Description:
When TaskExecutor register at ResourceManager, it takes the following 3 input
parameter:
1.
[
https://issues.apache.org/jira/browse/FLINK-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4535:
-
Description:
When TaskExecutor register at ResourceManager, it takes the following 3 input
parameter:
1.
[
https://issues.apache.org/jira/browse/FLINK-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4535:
-
Description:
When TaskExecutor register at ResourceManager, it takes the following 3 input
parameters:
zhangjing created FLINK-4606:
Summary: Integrate the new ResourceManager with the existing
FlinkResourceManager
Key: FLINK-4606
URL: https://issues.apache.org/jira/browse/FLINK-4606
Project: Flink
[
https://issues.apache.org/jira/browse/FLINK-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing reassigned FLINK-4489:
Assignee: zhangjing
> Implement TaskManager's SlotAllocationTable
>
zhangjing created FLINK-4653:
Summary: Refactor JobClientActor to adapt to the new Rpc framework
and new cluster managerment
Key: FLINK-4653
URL: https://issues.apache.org/jira/browse/FLINK-4653
Project:
[
https://issues.apache.org/jira/browse/FLINK-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing closed FLINK-4606.
Resolution: Fixed
> Integrate the new ResourceManager with the existing FlinkResourceManager
>
[
https://issues.apache.org/jira/browse/FLINK-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing reopened FLINK-4606:
--
> Integrate the new ResourceManager with the existing FlinkResourceManager
>
[
https://issues.apache.org/jira/browse/FLINK-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing closed FLINK-4633.
Resolution: Invalid
> Implement new Client
>
>
> Key: FLINK-4633
>
zhangjing created FLINK-4633:
Summary: Implement new Client
Key: FLINK-4633
URL: https://issues.apache.org/jira/browse/FLINK-4633
Project: Flink
Issue Type: Sub-task
Components:
[
https://issues.apache.org/jira/browse/FLINK-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing resolved FLINK-4537.
--
Resolution: Resolved
> ResourceManager registration with JobManager
>
[
https://issues.apache.org/jira/browse/FLINK-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing resolved FLINK-4535.
--
Resolution: Resolved
> ResourceManager registration with TaskExecutor
>
zhangjing created FLINK-4670:
Summary: Add watch mechanism on current RPC framework
Key: FLINK-4670
URL: https://issues.apache.org/jira/browse/FLINK-4670
Project: Flink
Issue Type: Sub-task
zhangjing created FLINK-4516:
Summary: ResourceManager leadership election
Key: FLINK-4516
URL: https://issues.apache.org/jira/browse/FLINK-4516
Project: Flink
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/FLINK-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing reassigned FLINK-4516:
Assignee: zhangjing
> ResourceManager leadership election
> ---
>
zhangjing created FLINK-4449:
Summary: Heartbeat Manager between ResourceManager and TaskExecutor
Key: FLINK-4449
URL: https://issues.apache.org/jira/browse/FLINK-4449
Project: Flink
Issue Type:
[
https://issues.apache.org/jira/browse/FLINK-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438437#comment-15438437
]
zhangjing edited comment on FLINK-4478 at 8/26/16 4:04 AM:
---
Hi [~till.rohrmann],
[
https://issues.apache.org/jira/browse/FLINK-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438437#comment-15438437
]
zhangjing commented on FLINK-4478:
--
Good abstraction.
> Implement heartbeat logic
>
[
https://issues.apache.org/jira/browse/FLINK-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-4489:
-
Assignee: (was: zhangjing)
> Implement TaskManager's SlotAllocationTable
>
[
https://issues.apache.org/jira/browse/FLINK-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714923#comment-15714923
]
zhangjing commented on FLINK-5220:
--
Hi Fabian, this jira and FLINK-3848 both about projection pushdown. I
[
https://issues.apache.org/jira/browse/FLINK-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714962#comment-15714962
]
zhangjing commented on FLINK-5226:
--
Hi Fabian, FlinkRuleSets already contains ProjectJoinTransposeRule,
[
https://issues.apache.org/jira/browse/FLINK-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714962#comment-15714962
]
zhangjing edited comment on FLINK-5226 at 12/2/16 12:12 PM:
Hi Fabian,
[
https://issues.apache.org/jira/browse/FLINK-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-5220:
-
Description: The jira is to do projection pushdown optimization. Please go
forward to the the design
zhangjing created FLINK-5220:
Summary: Flink SQL projection pushdown
Key: FLINK-5220
URL: https://issues.apache.org/jira/browse/FLINK-5220
Project: Flink
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/FLINK-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15717000#comment-15717000
]
zhangjing commented on FLINK-5220:
--
Hi, Fabian. I understand, I would close this jira. Thanks.
> Flink
[
https://issues.apache.org/jira/browse/FLINK-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing closed FLINK-5220.
Resolution: Duplicate
> Flink SQL projection pushdown
> -
>
>
[
https://issues.apache.org/jira/browse/FLINK-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-5394:
-
Description:
The estimateRowCount method of DataSetCalc didn't work now.
If I run the following code,
`
[
https://issues.apache.org/jira/browse/FLINK-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-5394:
-
Description:
The estimateRowCount method of DataSetCalc didn't work now.
If I run the following code,
`
[
https://issues.apache.org/jira/browse/FLINK-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-5394:
-
Description:
The estimateRowCount method of DataSetCalc didn't work now.
If I run the following code,
`
[
https://issues.apache.org/jira/browse/FLINK-4670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing closed FLINK-4670.
Resolution: Not A Problem
> Add watch mechanism on current RPC framework
>
[
https://issues.apache.org/jira/browse/FLINK-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-5394:
-
Description:
The estimateRowCount method of DataSetCalc didn't work now.
If I run the following code,
`
zhangjing created FLINK-5394:
Summary: the estimateRowCount method of DataSetCalc didn't work
Key: FLINK-5394
URL: https://issues.apache.org/jira/browse/FLINK-5394
Project: Flink
Issue Type: Bug
[
https://issues.apache.org/jira/browse/FLINK-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjing updated FLINK-5394:
-
Description:
The estimateRowCount method of DataSetCalc didn't work now.
If I run the following code,
`
79 matches
Mail list logo
