[jira] [Updated] (FLINK-14147) Reduce REST API Request/Response redundancy
[ https://issues.apache.org/jira/browse/FLINK-14147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-14147: --- Labels: auto-deprioritized-major auto-deprioritized-minor (was: auto-deprioritized-major stale-minor) Priority: Not a Priority (was: Minor) This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > Reduce REST API Request/Response redundancy > > > Key: FLINK-14147 > URL: https://issues.apache.org/jira/browse/FLINK-14147 > Project: Flink > Issue Type: Improvement > Components: Runtime / Web Frontend >Reporter: Yadong Xie >Priority: Not a Priority > Labels: auto-deprioritized-major, auto-deprioritized-minor > Attachments: 16_17_07__09_20_2019.jpg > > > 1. Redundancy Response > In the response of API /jobs/:jobid, the id and name in both plan and the > vertices data are exactly the same, it would waste a lot of network bandwidth > if the vertex graph is very big(1000+ vertex in a job). > !16_17_07__09_20_2019.jpg|width=427,height=279! > 2. Redundancy Request > In the current Web UI design, we have to query vertex number times to > display the low watermarks in the job graph. If the vertex number is very > large(1000+ sometimes), the Web UI will send 1000+ request to the REST API, > the max concurrent HTTP request in a browser is limited, it would bring a > long time delay for users. Test it, if there are more than 165 WarterMarks to > call will redirect to /bad-request, then 404. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-14147) Reduce REST API Request/Response redundancy
[ https://issues.apache.org/jira/browse/FLINK-14147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-14147: --- Labels: auto-deprioritized-major stale-minor (was: auto-deprioritized-major) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Reduce REST API Request/Response redundancy > > > Key: FLINK-14147 > URL: https://issues.apache.org/jira/browse/FLINK-14147 > Project: Flink > Issue Type: Improvement > Components: Runtime / Web Frontend >Reporter: Yadong Xie >Priority: Minor > Labels: auto-deprioritized-major, stale-minor > Attachments: 16_17_07__09_20_2019.jpg > > > 1. Redundancy Response > In the response of API /jobs/:jobid, the id and name in both plan and the > vertices data are exactly the same, it would waste a lot of network bandwidth > if the vertex graph is very big(1000+ vertex in a job). > !16_17_07__09_20_2019.jpg|width=427,height=279! > 2. Redundancy Request > In the current Web UI design, we have to query vertex number times to > display the low watermarks in the job graph. If the vertex number is very > large(1000+ sometimes), the Web UI will send 1000+ request to the REST API, > the max concurrent HTTP request in a browser is limited, it would bring a > long time delay for users. Test it, if there are more than 165 WarterMarks to > call will redirect to /bad-request, then 404. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-14147) Reduce REST API Request/Response redundancy
[ https://issues.apache.org/jira/browse/FLINK-14147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-14147: --- Priority: Minor (was: Major) > Reduce REST API Request/Response redundancy > > > Key: FLINK-14147 > URL: https://issues.apache.org/jira/browse/FLINK-14147 > Project: Flink > Issue Type: Improvement > Components: Runtime / Web Frontend >Reporter: Yadong Xie >Priority: Minor > Labels: auto-deprioritized-major > Attachments: 16_17_07__09_20_2019.jpg > > > 1. Redundancy Response > In the response of API /jobs/:jobid, the id and name in both plan and the > vertices data are exactly the same, it would waste a lot of network bandwidth > if the vertex graph is very big(1000+ vertex in a job). > !16_17_07__09_20_2019.jpg|width=427,height=279! > 2. Redundancy Request > In the current Web UI design, we have to query vertex number times to > display the low watermarks in the job graph. If the vertex number is very > large(1000+ sometimes), the Web UI will send 1000+ request to the REST API, > the max concurrent HTTP request in a browser is limited, it would bring a > long time delay for users. Test it, if there are more than 165 WarterMarks to > call will redirect to /bad-request, then 404. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-14147) Reduce REST API Request/Response redundancy
[ https://issues.apache.org/jira/browse/FLINK-14147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-14147: --- Labels: auto-deprioritized-major (was: stale-major) > Reduce REST API Request/Response redundancy > > > Key: FLINK-14147 > URL: https://issues.apache.org/jira/browse/FLINK-14147 > Project: Flink > Issue Type: Improvement > Components: Runtime / Web Frontend >Reporter: Yadong Xie >Priority: Major > Labels: auto-deprioritized-major > Attachments: 16_17_07__09_20_2019.jpg > > > 1. Redundancy Response > In the response of API /jobs/:jobid, the id and name in both plan and the > vertices data are exactly the same, it would waste a lot of network bandwidth > if the vertex graph is very big(1000+ vertex in a job). > !16_17_07__09_20_2019.jpg|width=427,height=279! > 2. Redundancy Request > In the current Web UI design, we have to query vertex number times to > display the low watermarks in the job graph. If the vertex number is very > large(1000+ sometimes), the Web UI will send 1000+ request to the REST API, > the max concurrent HTTP request in a browser is limited, it would bring a > long time delay for users. Test it, if there are more than 165 WarterMarks to > call will redirect to /bad-request, then 404. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-14147) Reduce REST API Request/Response redundancy
[ https://issues.apache.org/jira/browse/FLINK-14147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-14147: --- Labels: stale-major (was: ) > Reduce REST API Request/Response redundancy > > > Key: FLINK-14147 > URL: https://issues.apache.org/jira/browse/FLINK-14147 > Project: Flink > Issue Type: Improvement > Components: Runtime / Web Frontend >Reporter: Yadong Xie >Priority: Major > Labels: stale-major > Attachments: 16_17_07__09_20_2019.jpg > > > 1. Redundancy Response > In the response of API /jobs/:jobid, the id and name in both plan and the > vertices data are exactly the same, it would waste a lot of network bandwidth > if the vertex graph is very big(1000+ vertex in a job). > !16_17_07__09_20_2019.jpg|width=427,height=279! > 2. Redundancy Request > In the current Web UI design, we have to query vertex number times to > display the low watermarks in the job graph. If the vertex number is very > large(1000+ sometimes), the Web UI will send 1000+ request to the REST API, > the max concurrent HTTP request in a browser is limited, it would bring a > long time delay for users. Test it, if there are more than 165 WarterMarks to > call will redirect to /bad-request, then 404. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-14147) Reduce REST API Request/Response redundancy
[ https://issues.apache.org/jira/browse/FLINK-14147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14147: --- Description: 1. Redundancy Response In the response of API /jobs/:jobid, the id and name in both plan and the vertices data are exactly the same, it would waste a lot of network bandwidth if the vertex graph is very big(1000+ vertex in a job). !16_17_07__09_20_2019.jpg|width=427,height=279! 2. Redundancy Request In the current Web UI design, we have to query vertex number times to display the low watermarks in the job graph. If the vertex number is very large(1000+ sometimes), the Web UI will send 1000+ request to the REST API, the max concurrent HTTP request in a browser is limited, it would bring a long time delay for users. Test it, if there are more than 165 WarterMarks to call will redirect to /bad-request, then 404. was: 1. Redundancy Response In the response of API /jobs/:jobid, the id and name in both plan and the vertices data are exactly the same, it would waste a lot of network bandwidth if the vertex graph is very big(1000+ vertex in a job). !16_17_07__09_20_2019.jpg|width=427,height=279! 2. Redundancy Request In the current Web UI design, we have to query vertex number times to display the low watermarks in the job graph. If the vertex number is very large(1000+ sometimes), the Web UI will send 1000+ request to the REST API, the max concurrent HTTP request in a browser is limited, it would bring a long time delay for users. > Reduce REST API Request/Response redundancy > > > Key: FLINK-14147 > URL: https://issues.apache.org/jira/browse/FLINK-14147 > Project: Flink > Issue Type: Improvement > Components: Runtime / Web Frontend >Reporter: Yadong Xie >Priority: Major > Attachments: 16_17_07__09_20_2019.jpg > > > 1. Redundancy Response > In the response of API /jobs/:jobid, the id and name in both plan and the > vertices data are exactly the same, it would waste a lot of network bandwidth > if the vertex graph is very big(1000+ vertex in a job). > !16_17_07__09_20_2019.jpg|width=427,height=279! > 2. Redundancy Request > In the current Web UI design, we have to query vertex number times to > display the low watermarks in the job graph. If the vertex number is very > large(1000+ sometimes), the Web UI will send 1000+ request to the REST API, > the max concurrent HTTP request in a browser is limited, it would bring a > long time delay for users. Test it, if there are more than 165 WarterMarks to > call will redirect to /bad-request, then 404. -- This message was sent by Atlassian Jira (v8.3.4#803005)
