[jira] [Commented] (FLINK-10115) Upload Project to WEB UI has issue

2018-08-15 Thread Yazdan Shirvany (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-10115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581087#comment-16581087
 ] 

Yazdan Shirvany commented on FLINK-10115:
-

[~Zentol] yes, this issue is only for 1.6.0. haven't seen it for other versions.

and it's a blocker for working with Web UI.

> Upload Project to WEB UI has issue
> --
>
> Key: FLINK-10115
> URL: https://issues.apache.org/jira/browse/FLINK-10115
> Project: Flink
>  Issue Type: Bug
>  Components: Webfrontend
>Affects Versions: 1.6.0
>Reporter: Yazdan Shirvany
>Priority: Major
> Fix For: 1.6.1
>
>
> Uploading jar files via WEB UI not working. After {{initializing upload...}} 
> it only shows {{saving...}} and file never shows up on UI to be able to 
> submit it



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-10115) Upload Project to WEB UI has issue

2018-08-09 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-10115:
---

 Summary: Upload Project to WEB UI has issue
 Key: FLINK-10115
 URL: https://issues.apache.org/jira/browse/FLINK-10115
 Project: Flink
  Issue Type: Bug
  Components: Webfrontend
Reporter: Yazdan Shirvany
 Fix For: 1.6.0


Uploading jar files via WEB UI not working. After {{initializing upload...}} it 
only shows {{saving...}} and file never shows up on UI to be able to submit it



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-10112) https://ci.apache.org title for release 1.6 shows 1.6-SNAPSHOT

2018-08-09 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-10112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-10112:

Description: Flink 1.6 has been released but I still can see 1.6-SNAPSHOT 
on https://ci.apache.org/projects/flink/flink-docs-release-1.6/ and when I 
click to any of the options it redirects me to master docs with 1.7-SNAPSHOT 
title  (was: Flink 1.6 has been released but I still can see 1.6-SNAPSHOT on 
[https://ci.apache.org/] and when I click to any of the options it redirects me 
to master docs with 1.7-SNAPSHOT title)

> https://ci.apache.org title for release 1.6 shows 1.6-SNAPSHOT
> --
>
> Key: FLINK-10112
> URL: https://issues.apache.org/jira/browse/FLINK-10112
> Project: Flink
>  Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Yazdan Shirvany
>Priority: Critical
>
> Flink 1.6 has been released but I still can see 1.6-SNAPSHOT on 
> https://ci.apache.org/projects/flink/flink-docs-release-1.6/ and when I click 
> to any of the options it redirects me to master docs with 1.7-SNAPSHOT title



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-10112) https://ci.apache.org title for release 1.6 shows 1.6-SNAPSHOT

2018-08-09 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-10112:
---

 Summary: https://ci.apache.org title for release 1.6 shows 
1.6-SNAPSHOT
 Key: FLINK-10112
 URL: https://issues.apache.org/jira/browse/FLINK-10112
 Project: Flink
  Issue Type: Bug
Affects Versions: 1.6.0
Reporter: Yazdan Shirvany


Flink 1.6 has been released but I still can see 1.6-SNAPSHOT on 
[https://ci.apache.org/] and when I click to any of the options it redirects me 
to master docs with 1.7-SNAPSHOT title



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FLINK-9848) When Parallelism more than available task slots Flink stays idle

2018-07-13 Thread Yazdan Shirvany (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543681#comment-16543681
 ] 

Yazdan Shirvany commented on FLINK-9848:


Actually I re-tried with multiple examples and seems only 
{{batch/WordCount.jar}} can be successful when {{parallelism > available slots}}

> When Parallelism more than available task slots Flink stays idle
> 
>
> Key: FLINK-9848
> URL: https://issues.apache.org/jira/browse/FLINK-9848
> Project: Flink
>  Issue Type: Bug
>  Components: Cluster Management
>Affects Versions: 1.5.0, 1.5.1
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Critical
>
> For version 1.4.x when select Parallelism > Available task Slots, Flink throw 
> bellow error right away 
> {{NoResourceAvailableException: Not enough free slots available to run the 
> job}}
>   
>  but for version 1.5.x there are two different behaviors: Sometimes job ran 
> successfully and sometimes it throw bellow error after 5 minutes 
>  
> {{org.apache.flink.runtime.jobmanager.scheduler.NoResourceAvailableException: 
> Could not allocate all requires slots within timeout of 30 ms. Slots 
> required: 5, slots allocated: 2}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2018-07-13 Thread Yazdan Shirvany (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543402#comment-16543402
 ] 

Yazdan Shirvany commented on FLINK-4319:


[~till.rohrmann] Thanks a lot for the info. I will start look into `Distributed 
Coordination` component to see where I will be able to contribute.

 

 

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>Priority: Major
>  Labels: flip-6
> Fix For: 1.5.0
>
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9848) When Parallelism more than available task slots Flink stays idle

2018-07-13 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9848:
---
Description: 
For version 1.4.x when select Parallelism > Available task Slots, Flink throw 
bellow error right away 

{{NoResourceAvailableException: Not enough free slots available to run the job}}
  
 but for version 1.5.x there are two different behaviors: Sometimes job ran 
successfully and sometimes it throw bellow error after 5 minutes 

 
{{org.apache.flink.runtime.jobmanager.scheduler.NoResourceAvailableException: 
Could not allocate all requires slots within timeout of 30 ms. Slots 
required: 5, slots allocated: 2}}

  was:
For version 1.4.x when select Parallelism > Available task Slots, Flink throw 
bellow error right away 


{{NoResourceAvailableException: Not enough free slots available to run the job}}
  
 but for version 1.5.x there are two different behaviors: Sometimes job ran 
successfully and sometimes it throw bellow error after 5 minutes  
org.apache.flink.runtime.jobmanager.scheduler.NoResourceAvailableException: 
Could not allocate all requires slots within timeout of 30 ms. Slots 
required: 5, slots allocated: 2


> When Parallelism more than available task slots Flink stays idle
> 
>
> Key: FLINK-9848
> URL: https://issues.apache.org/jira/browse/FLINK-9848
> Project: Flink
>  Issue Type: Bug
>  Components: Cluster Management
>Affects Versions: 1.5.0, 1.5.1
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Critical
>
> For version 1.4.x when select Parallelism > Available task Slots, Flink throw 
> bellow error right away 
> {{NoResourceAvailableException: Not enough free slots available to run the 
> job}}
>   
>  but for version 1.5.x there are two different behaviors: Sometimes job ran 
> successfully and sometimes it throw bellow error after 5 minutes 
>  
> {{org.apache.flink.runtime.jobmanager.scheduler.NoResourceAvailableException: 
> Could not allocate all requires slots within timeout of 30 ms. Slots 
> required: 5, slots allocated: 2}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9848) When Parallelism more than available task slots Flink stays idle

2018-07-13 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9848:
---
Attachment: (was: idleJob.jpg)

> When Parallelism more than available task slots Flink stays idle
> 
>
> Key: FLINK-9848
> URL: https://issues.apache.org/jira/browse/FLINK-9848
> Project: Flink
>  Issue Type: Bug
>  Components: Cluster Management
>Affects Versions: 1.5.0, 1.5.1
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Critical
>
> For version 1.4.x when select Parallelism > Available task Slots, Flink throw 
> bellow error right away 
> {{NoResourceAvailableException: Not enough free slots available to run the 
> job}}
>   
>  but for version 1.5.x there are two different behaviors: Sometimes job ran 
> successfully and sometimes it throw bellow error after 5 minutes  
> org.apache.flink.runtime.jobmanager.scheduler.NoResourceAvailableException: 
> Could not allocate all requires slots within timeout of 30 ms. Slots 
> required: 5, slots allocated: 2



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9848) When Parallelism more than available task slots Flink stays idle

2018-07-13 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9848:
---
Description: 
For version 1.4.x when select Parallelism > Available task Slots, Flink throw 
bellow error right away 


{{NoResourceAvailableException: Not enough free slots available to run the job}}
  
 but for version 1.5.x there are two different behaviors: Sometimes job ran 
successfully and sometimes it throw bellow error after 5 minutes  
org.apache.flink.runtime.jobmanager.scheduler.NoResourceAvailableException: 
Could not allocate all requires slots within timeout of 30 ms. Slots 
required: 5, slots allocated: 2

  was:
For version 1.4.x when select Parallelism > Available task Slots Flink throw 
bellow error
NoResourceAvailableException: Not enough free slots available to run the job
 
but for version 1.5.x there are two different behaviors: Sometimes job ran 
successfully and sometimes it stay in "Running" status for a log time (I waited 
more than 3 minutes) and never throw error
 
In bellow image Available task slots is 1 and  job has been submitted with 
Parallelism = 4
Flink Version 1.5.1 !idleJob.jpg!


> When Parallelism more than available task slots Flink stays idle
> 
>
> Key: FLINK-9848
> URL: https://issues.apache.org/jira/browse/FLINK-9848
> Project: Flink
>  Issue Type: Bug
>  Components: Cluster Management
>Affects Versions: 1.5.0, 1.5.1
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Critical
> Attachments: idleJob.jpg
>
>
> For version 1.4.x when select Parallelism > Available task Slots, Flink throw 
> bellow error right away 
> {{NoResourceAvailableException: Not enough free slots available to run the 
> job}}
>   
>  but for version 1.5.x there are two different behaviors: Sometimes job ran 
> successfully and sometimes it throw bellow error after 5 minutes  
> org.apache.flink.runtime.jobmanager.scheduler.NoResourceAvailableException: 
> Could not allocate all requires slots within timeout of 30 ms. Slots 
> required: 5, slots allocated: 2



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9848) When Parallelism more than available task slots Flink stays idle

2018-07-13 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9848:
---
Attachment: idleJob.jpg

> When Parallelism more than available task slots Flink stays idle
> 
>
> Key: FLINK-9848
> URL: https://issues.apache.org/jira/browse/FLINK-9848
> Project: Flink
>  Issue Type: Bug
>  Components: Cluster Management
>Affects Versions: 1.5.0, 1.5.1
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Critical
> Attachments: idleJob.jpg
>
>
> For version 1.4.x when select Parallelism > Available task Slots Flink throw 
> bellow error
> NoResourceAvailableException: Not enough free slots available to run the job
>  
> but for version 1.5.x there are two different behaviors: Sometimes job ran 
> successfully and sometimes it stay in "Running" status for a log time (I 
> waited more than 3 minutes) and never throw error
>  
> In bellow image Available task slots is 1 and  job has been submitted with 
> Parallelism = 4
> Flink Version 1.5.1 !idleJob.jpg!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9848) When Parallelism more than available task slots Flink stays idle

2018-07-13 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9848:
--

 Summary: When Parallelism more than available task slots Flink 
stays idle
 Key: FLINK-9848
 URL: https://issues.apache.org/jira/browse/FLINK-9848
 Project: Flink
  Issue Type: Bug
  Components: Cluster Management
Affects Versions: 1.5.1, 1.5.0
Reporter: Yazdan Shirvany
Assignee: Yazdan Shirvany
 Attachments: idleJob.jpg

For version 1.4.x when select Parallelism > Available task Slots Flink throw 
bellow error
NoResourceAvailableException: Not enough free slots available to run the job
 
but for version 1.5.x there are two different behaviors: Sometimes job ran 
successfully and sometimes it stay in "Running" status for a log time (I waited 
more than 3 minutes) and never throw error
 
In bellow image Available task slots is 1 and  job has been submitted with 
Parallelism = 4
Flink Version 1.5.1 !idleJob.jpg!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2018-07-11 Thread Yazdan Shirvany (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540220#comment-16540220
 ] 

Yazdan Shirvany commented on FLINK-4319:


[~till.rohrmann] I am very interested to start contributing in this effort and 
I am wondering where should I start. I would appreciate if you guide me here 
and let me know which task/subtask is good to start inorder to understand the 
whole picture as well as be able to contribute :)

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>Priority: Major
>  Labels: flip-6
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9771) "Show Plan" option under Submit New Job in WebUI not working

2018-07-05 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9771:
--

 Summary:  "Show Plan" option under Submit New Job in WebUI not 
working 
 Key: FLINK-9771
 URL: https://issues.apache.org/jira/browse/FLINK-9771
 Project: Flink
  Issue Type: Bug
  Components: Job-Submission, Webfrontend
Affects Versions: 1.5.0, 1.5.1, 1.6.0
Reporter: Yazdan Shirvany


{{Show Plan}} button under {{Submit new job}} in WebUI not working.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9679) Implement AvroSerializationSchema

2018-06-27 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9679:
--

 Summary: Implement AvroSerializationSchema
 Key: FLINK-9679
 URL: https://issues.apache.org/jira/browse/FLINK-9679
 Project: Flink
  Issue Type: Improvement
Affects Versions: 1.6.0
Reporter: Yazdan Shirvany
Assignee: Yazdan Shirvany


Implement AvroSerializationSchema using Confluent Schema Registry



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9551) FlinkCEP Scala Combining Patterns table has a missing pattern

2018-06-07 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9551:
---
Summary: FlinkCEP Scala Combining Patterns table has a missing pattern  
(was: FlinkCEP Scala Combining Patterns table has two missing pattern)

> FlinkCEP Scala Combining Patterns table has a missing pattern
> -
>
> Key: FLINK-9551
> URL: https://issues.apache.org/jira/browse/FLINK-9551
> Project: Flink
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Minor
>
> in FlinkCEP documentation section related to {{Combining Patterns}} Scala 
> Table has a missing patterns compare to Java table
> {{begin(#pattern_sequence)}}
> and also 
> {{begin()}} pattern has missing {{#name}} params



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9551) FlinkCEP Scala Combining Patterns table has two missing pattern

2018-06-07 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9551:
--

 Summary: FlinkCEP Scala Combining Patterns table has two missing 
pattern
 Key: FLINK-9551
 URL: https://issues.apache.org/jira/browse/FLINK-9551
 Project: Flink
  Issue Type: Improvement
  Components: Documentation
Reporter: Yazdan Shirvany
Assignee: Yazdan Shirvany


in FlinkCEP documentation section related to {{Combining Patterns}} Scala Table 
has a missing patterns compare to Java table

{{begin(#pattern_sequence)}}
and also 
{{begin()}} pattern has missing {{#name}} params




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9550) FlinkCEP snippet example has some syntax errors

2018-06-07 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9550:
--

 Summary: FlinkCEP snippet example has some syntax errors
 Key: FLINK-9550
 URL: https://issues.apache.org/jira/browse/FLINK-9550
 Project: Flink
  Issue Type: Improvement
Reporter: Yazdan Shirvany
Assignee: Yazdan Shirvany


I tried to work with FlinckCEP documentarians and my assumption was the snippet 
example should work but I got some syntax errors that needed to be fix.  




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9549) Fix FlickCEP Docs broken link and minor style changes

2018-06-07 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9549:
--

 Summary: Fix FlickCEP Docs broken link and minor style changes
 Key: FLINK-9549
 URL: https://issues.apache.org/jira/browse/FLINK-9549
 Project: Flink
  Issue Type: Improvement
Reporter: Yazdan Shirvany
Assignee: Yazdan Shirvany






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9517) Fixing broken links on CLI and Upgrade Docs

2018-06-04 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9517:
---
Fix Version/s: 1.5.0
   1.4.1
   1.4.2

> Fixing broken links on CLI and Upgrade Docs
> ---
>
> Key: FLINK-9517
> URL: https://issues.apache.org/jira/browse/FLINK-9517
> Project: Flink
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Trivial
> Fix For: 1.5.0, 1.4.1, 1.4.2
>
>
> broken links for cli and upgrade page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9517) Fixing broken links on CLI and Upgrade Docs

2018-06-04 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9517:
---
Component/s: Documentation

> Fixing broken links on CLI and Upgrade Docs
> ---
>
> Key: FLINK-9517
> URL: https://issues.apache.org/jira/browse/FLINK-9517
> Project: Flink
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Trivial
> Fix For: 1.5.0, 1.4.1, 1.4.2
>
>
> broken links for cli and upgrade page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9518) SSL setup Docs config example has wrong keys password

2018-06-04 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9518:
---
Description: In creating keystores and turststore section password is set 
to {{password}} but in setup config section it is \{{abc123}}  (was: In 
creating keystores and turststore section password is set to \{{password}} but 
in setup config section it is \{{abc123}})

> SSL setup Docs config example has wrong keys password 
> --
>
> Key: FLINK-9518
> URL: https://issues.apache.org/jira/browse/FLINK-9518
> Project: Flink
>  Issue Type: Improvement
>  Components: Documentation
>Affects Versions: 1.5.0, 1.4.1, 1.4.2
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Minor
>
> In creating keystores and turststore section password is set to {{password}} 
> but in setup config section it is \{{abc123}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9518) SSL setup Docs config example has wrong keys password

2018-06-04 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9518:
---
Description: In creating keystores and turststore section password is set 
to {{password}} but in setup config section it is {{abc123}}  (was: In creating 
keystores and turststore section password is set to {{password}} but in setup 
config section it is \{{abc123}})

> SSL setup Docs config example has wrong keys password 
> --
>
> Key: FLINK-9518
> URL: https://issues.apache.org/jira/browse/FLINK-9518
> Project: Flink
>  Issue Type: Improvement
>  Components: Documentation
>Affects Versions: 1.5.0, 1.4.1, 1.4.2
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Minor
>
> In creating keystores and turststore section password is set to {{password}} 
> but in setup config section it is {{abc123}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9518) SSL setup Docs config example has wrong keys password

2018-06-04 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9518:
--

 Summary: SSL setup Docs config example has wrong keys password 
 Key: FLINK-9518
 URL: https://issues.apache.org/jira/browse/FLINK-9518
 Project: Flink
  Issue Type: Improvement
  Components: Documentation
Affects Versions: 1.4.2, 1.4.1, 1.5.0
Reporter: Yazdan Shirvany
Assignee: Yazdan Shirvany


In creating keystores and turststore section password is set to \{{password}} 
but in setup config section it is \{{abc123}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9517) Fixing broken links on CLI and Upgrade Docs

2018-06-04 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9517:
---
Description: broken links for cli and upgrade page  (was: broken links for 
cli page)

> Fixing broken links on CLI and Upgrade Docs
> ---
>
> Key: FLINK-9517
> URL: https://issues.apache.org/jira/browse/FLINK-9517
> Project: Flink
>  Issue Type: Improvement
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Trivial
>
> broken links for cli and upgrade page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9517) Fixing broken links on CLI and Upgrade Docs

2018-06-04 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9517:
---
Summary: Fixing broken links on CLI and Upgrade Docs  (was: Fixing broken 
links on CLI Docs)

> Fixing broken links on CLI and Upgrade Docs
> ---
>
> Key: FLINK-9517
> URL: https://issues.apache.org/jira/browse/FLINK-9517
> Project: Flink
>  Issue Type: Improvement
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Trivial
>
> broken links for cli page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9517) Fixing broken links on CLI Docs

2018-06-04 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9517:
--

 Summary: Fixing broken links on CLI Docs
 Key: FLINK-9517
 URL: https://issues.apache.org/jira/browse/FLINK-9517
 Project: Flink
  Issue Type: Improvement
Reporter: Yazdan Shirvany
Assignee: Yazdan Shirvany


broken links for cli page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FLINK-9509) CLI usage are not same as CLI docs

2018-06-04 Thread Yazdan Shirvany (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16499988#comment-16499988
 ] 

Yazdan Shirvany commented on FLINK-9509:


[~Zentol] Thank you! I looked for similar ticket before open it and seems I 
have missed FLINK-9109.

> CLI usage are not same as CLI docs
> --
>
> Key: FLINK-9509
> URL: https://issues.apache.org/jira/browse/FLINK-9509
> Project: Flink
>  Issue Type: Improvement
>  Components: Client, Documentation
>Affects Versions: 1.5.0
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Major
>
> `./bin/flink  -h`  for version 1.5.0 output is different from document usage 
> on CLI here
> [https://ci.apache.org/projects/flink/flink-docs-release-1.5/ops/cli.html#usage]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9509) CLI usage are not same as CLI docs

2018-06-03 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9509:
---
Component/s: Documentation
 Client

> CLI usage are not same as CLI docs
> --
>
> Key: FLINK-9509
> URL: https://issues.apache.org/jira/browse/FLINK-9509
> Project: Flink
>  Issue Type: Improvement
>  Components: Client, Documentation
>Affects Versions: 1.5.0
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Major
>
> `./bin/flink  -h`  for version 1.5.0 output is different from document usage 
> on CLI here
> [https://ci.apache.org/projects/flink/flink-docs-release-1.5/ops/cli.html#usage]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9509) CLI usage are not same as CLI docs

2018-06-03 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9509:
--

 Summary: CLI usage are not same as CLI docs
 Key: FLINK-9509
 URL: https://issues.apache.org/jira/browse/FLINK-9509
 Project: Flink
  Issue Type: Improvement
Affects Versions: 1.5.0
Reporter: Yazdan Shirvany
Assignee: Yazdan Shirvany


`./bin/flink  -h`  for version 1.5.0 output is different from document usage on 
CLI here

[https://ci.apache.org/projects/flink/flink-docs-release-1.5/ops/cli.html#usage]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9508) General Spell Check on Flink Docs

2018-06-03 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9508:
--

 Summary: General Spell Check on Flink Docs
 Key: FLINK-9508
 URL: https://issues.apache.org/jira/browse/FLINK-9508
 Project: Flink
  Issue Type: Improvement
  Components: Documentation
Affects Versions: 1.4.2, 1.4.1, 1.5.0
Reporter: Yazdan Shirvany
Assignee: Yazdan Shirvany


Fixing Flink docs misspelling 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (FLINK-9505) End-to-end test: Flink-Example module [flink-examples-streaming]

2018-06-02 Thread Yazdan Shirvany (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-9505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16499099#comment-16499099
 ] 

Yazdan Shirvany edited comment on FLINK-9505 at 6/2/18 3:33 PM:


[~Zentol]

As we discussed (on quickstart PR), you mentioned that Flink-Example module 
also should have end-2-end tests. I opened this ticket to track it.

How you like to approach this?

I was thinking to have one test script for each class on each submodule as the 
nature of each test example is different.

 

 


was (Author: yazdanjs):
[~Zentol]

As we discussed (on quickstart PR), you mentioned that Flink-Example module 
also should have end-2-end tests. I opened this ticket to track it.

How you like to approach this?

I was thinking to have one test script for each submodule [e.g, 
flink-examples-streaming] that we can pass in parameters such as ClassName, 
Type, etc. for testing each example on that submodule in nightly tests.

 

 

> End-to-end test: Flink-Example module [flink-examples-streaming]
> 
>
> Key: FLINK-9505
> URL: https://issues.apache.org/jira/browse/FLINK-9505
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Major
>
> Write End-to-End test for Flink-Example -  [flink-examples-streaming] 
> submodule



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (FLINK-9505) End-to-end test: Flink-Example module [flink-examples-streaming]

2018-06-02 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany reassigned FLINK-9505:
--

Assignee: Yazdan Shirvany

> End-to-end test: Flink-Example module [flink-examples-streaming]
> 
>
> Key: FLINK-9505
> URL: https://issues.apache.org/jira/browse/FLINK-9505
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Major
>
> Write End-to-End test for Flink-Example -  [flink-examples-streaming] 
> submodule



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FLINK-9505) End-to-end test: Flink-Example module [flink-examples-streaming]

2018-06-02 Thread Yazdan Shirvany (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-9505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16499099#comment-16499099
 ] 

Yazdan Shirvany commented on FLINK-9505:


[~Zentol]

As we discussed (on quickstart PR), you mentioned that Flink-Example module 
also should have end-2-end tests. I opened this ticket to track it.

How you like to approach this?

I was thinking to have one test script for each submodule [e.g, 
flink-examples-streaming] that we can pass in parameters such as ClassName, 
Type, etc. for testing each example on that submodule in nightly tests.

 

 

> End-to-end test: Flink-Example module [flink-examples-streaming]
> 
>
> Key: FLINK-9505
> URL: https://issues.apache.org/jira/browse/FLINK-9505
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Yazdan Shirvany
>Priority: Major
>
> Write End-to-End test for Flink-Example -  [flink-examples-streaming] 
> submodule



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9505) End-to-end test: Flink-Example module [flink-examples-streaming]

2018-06-02 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9505:
---
Description: Write End-to-End test for Flink-Example -  
[flink-examples-streaming] submodule  (was: Write End-to-End test for 
Flink-Example submodules
 *  flink-examples-batch
 * 
 * flink-examples-table )

> End-to-end test: Flink-Example module [flink-examples-streaming]
> 
>
> Key: FLINK-9505
> URL: https://issues.apache.org/jira/browse/FLINK-9505
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Yazdan Shirvany
>Priority: Major
>
> Write End-to-End test for Flink-Example -  [flink-examples-streaming] 
> submodule



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9505) End-to-end test: Flink-Example module [flink-examples-streaming]

2018-06-02 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9505:
---
Summary: End-to-end test: Flink-Example module [flink-examples-streaming]  
(was: End-to-end test: Flink-Example module)

> End-to-end test: Flink-Example module [flink-examples-streaming]
> 
>
> Key: FLINK-9505
> URL: https://issues.apache.org/jira/browse/FLINK-9505
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Yazdan Shirvany
>Priority: Major
>
> Write End-to-End test for Flink-Example submodules
>  *  flink-examples-batch
>  * 
>  * flink-examples-table 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9505) End-to-end test: Flink-Example module

2018-06-02 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9505:
---
Description: 
Write End-to-End test for Flink-Example submodules
 *  flink-examples-batch
 * 
 * flink-examples-table 

  was:
Write End-to-End test for Flink-Example submodules
 *  flink-examples-batch
 * flink-examples-streaming
 * flink-examples-table 


> End-to-end test: Flink-Example module
> -
>
> Key: FLINK-9505
> URL: https://issues.apache.org/jira/browse/FLINK-9505
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Yazdan Shirvany
>Priority: Major
>
> Write End-to-End test for Flink-Example submodules
>  *  flink-examples-batch
>  * 
>  * flink-examples-table 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9505) End-to-end test: Flink-Example module

2018-06-02 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9505:
---
Description: 
Write End-to-End test for Flink-Example submodules
 *  flink-examples-batch
 * flink-examples-streaming
 * flink-examples-table 

  was:
Write End-to-End test for Flink-Example submodules

- flink-examples-batch

- flink-examples-streaming

- flink-examples-table 


> End-to-end test: Flink-Example module
> -
>
> Key: FLINK-9505
> URL: https://issues.apache.org/jira/browse/FLINK-9505
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Yazdan Shirvany
>Priority: Major
>
> Write End-to-End test for Flink-Example submodules
>  *  flink-examples-batch
>  * flink-examples-streaming
>  * flink-examples-table 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9505) End-to-end test: Flink-Example module

2018-06-02 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9505:
---
Description: 
Write End-to-End test for Flink-Example submodules

- flink-examples-batch

- flink-examples-streaming

- flink-examples-table 

> End-to-end test: Flink-Example module
> -
>
> Key: FLINK-9505
> URL: https://issues.apache.org/jira/browse/FLINK-9505
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Yazdan Shirvany
>Priority: Major
>
> Write End-to-End test for Flink-Example submodules
> - flink-examples-batch
> - flink-examples-streaming
> - flink-examples-table 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9505) End-to-end test: Flink-

2018-06-02 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9505:
---
Summary: End-to-end test: Flink-  (was: End-to-end test: Quickstarts for 
Scala)

> End-to-end test: Flink-
> ---
>
> Key: FLINK-9505
> URL: https://issues.apache.org/jira/browse/FLINK-9505
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Yazdan Shirvany
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9505) End-to-end test: Quickstarts for Scala

2018-06-02 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9505:
--

 Summary: End-to-end test: Quickstarts for Scala
 Key: FLINK-9505
 URL: https://issues.apache.org/jira/browse/FLINK-9505
 Project: Flink
  Issue Type: Sub-task
Reporter: Yazdan Shirvany






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9505) End-to-end test: Flink-Example module

2018-06-02 Thread Yazdan Shirvany (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-9505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9505:
---
Summary: End-to-end test: Flink-Example module  (was: End-to-end test: 
Flink-)

> End-to-end test: Flink-Example module
> -
>
> Key: FLINK-9505
> URL: https://issues.apache.org/jira/browse/FLINK-9505
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Yazdan Shirvany
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (FLINK-9451) End-to-end test: Scala Quickstarts

2018-05-28 Thread Yazdan Shirvany (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-9451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany reassigned FLINK-9451:
--

Assignee: Yazdan Shirvany

> End-to-end test: Scala Quickstarts
> --
>
> Key: FLINK-9451
> URL: https://issues.apache.org/jira/browse/FLINK-9451
> Project: Flink
>  Issue Type: Sub-task
>  Components: Quickstarts
>Affects Versions: 1.5.0, 1.4.1, 1.4.2
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Blocker
>
> We could add an end-to-end test which verifies Flink's quickstarts scala. It 
> should do the following:
>  # create a new Flink project using the quickstarts archetype
>  # add a new Flink dependency to the {{pom.xml}} (e.g. Flink connector or 
> library)
>  # run {{mvn clean package -Pbuild-jar}}
>  # verify that no core dependencies are contained in the jar file
>  # Run the program



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9451) End-to-end test: Scala Quickstarts

2018-05-27 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9451:
--

 Summary: End-to-end test: Scala Quickstarts
 Key: FLINK-9451
 URL: https://issues.apache.org/jira/browse/FLINK-9451
 Project: Flink
  Issue Type: Sub-task
  Components: Quickstarts
Affects Versions: 1.4.2, 1.4.1, 1.5.0
Reporter: Yazdan Shirvany


We could add an end-to-end test which verifies Flink's quickstarts scala. It 
should do the following:
 # create a new Flink project using the quickstarts archetype
 # add a new Flink dependency to the {{pom.xml}} (e.g. Flink connector or 
library)
 # run {{mvn clean package -Pbuild-jar}}
 # verify that no core dependencies are contained in the jar file
 # Run the program



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (FLINK-8970) Add more automated end-to-end tests

2018-05-27 Thread Yazdan Shirvany (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-8970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany reassigned FLINK-8970:
--

Assignee: Yazdan Shirvany

> Add more automated end-to-end tests
> ---
>
> Key: FLINK-8970
> URL: https://issues.apache.org/jira/browse/FLINK-8970
> Project: Flink
>  Issue Type: Improvement
>  Components: Tests
>Reporter: Till Rohrmann
>Assignee: Yazdan Shirvany
>Priority: Major
> Fix For: 1.6.0
>
>
> In order to improve Flink's test coverage and make releasing easier, we 
> should add more automated end-to-end tests which test Flink more like a user 
> would interact with the system. Additionally, these end-to-end tests should 
> test the integration of various other systems with Flink.
> With FLINK-6539, we added a new module \{{flink-end-to-end-tests}} which 
> contains the set of currently available end-to-end tests.
> With FLINK-8911, a script was added to trigger these tests.
>  
> This issue is an umbrella issue collecting all different end-to-end tests 
> which we want to add to the Flink repository.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (FLINK-8654) Extend quickstart docs on how to submit jobs

2018-05-26 Thread Yazdan Shirvany (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-8654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany reassigned FLINK-8654:
--

Assignee: Yazdan Shirvany

> Extend quickstart docs on how to submit jobs
> 
>
> Key: FLINK-8654
> URL: https://issues.apache.org/jira/browse/FLINK-8654
> Project: Flink
>  Issue Type: Improvement
>  Components: Documentation, Quickstarts
>Affects Versions: 1.5.0
>Reporter: Chesnay Schepler
>Assignee: Yazdan Shirvany
>Priority: Major
>
> The quickstart documentation explains how to setup the project, build the jar 
> and run things in the IDE, but neither explains how to submit the jar to a 
> cluster nor guides the user to where he could find this information (like the 
> CLI docs).
> Additionally, the quickstart poms should also contain the commands for 
> submitting the jar to a cluster, in particular how to select a main-class if 
> it wasn't set in the pom. (-c CLI flag)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (FLINK-8983) End-to-end test: Confluent schema registry

2018-05-19 Thread Yazdan Shirvany (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-8983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany reassigned FLINK-8983:
--

Assignee: Yazdan Shirvany

> End-to-end test: Confluent schema registry
> --
>
> Key: FLINK-8983
> URL: https://issues.apache.org/jira/browse/FLINK-8983
> Project: Flink
>  Issue Type: Sub-task
>  Components: Kafka Connector, Tests
>Reporter: Till Rohrmann
>Assignee: Yazdan Shirvany
>Priority: Critical
>
> It would be good to add an end-to-end test which verifies that Flink is able 
> to work together with the Confluent schema registry. In order to do that we 
> have to setup a Kafka cluster and write a Flink job which reads from the 
> Confluent schema registry producing an Avro type.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FLINK-8983) End-to-end test: Confluent schema registry

2018-05-18 Thread Yazdan Shirvany (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-8983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481458#comment-16481458
 ] 

Yazdan Shirvany commented on FLINK-8983:


[~till.rohrmann] is it ok to assign this to myself?

> End-to-end test: Confluent schema registry
> --
>
> Key: FLINK-8983
> URL: https://issues.apache.org/jira/browse/FLINK-8983
> Project: Flink
>  Issue Type: Sub-task
>  Components: Kafka Connector, Tests
>Reporter: Till Rohrmann
>Priority: Critical
>
> It would be good to add an end-to-end test which verifies that Flink is able 
> to work together with the Confluent schema registry. In order to do that we 
> have to setup a Kafka cluster and write a Flink job which reads from the 
> Confluent schema registry producing an Avro type.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FLINK-8654) Extend quickstart docs on how to submit jobs

2018-05-18 Thread Yazdan Shirvany (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-8654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481456#comment-16481456
 ] 

Yazdan Shirvany commented on FLINK-8654:


[~Zentol] is this still valid? If yes I would like to assign it to myself and 
work on it

Should the CLI part goes here :

[https://ci.apache.org/projects/flink/flink-docs-release-1.4/quickstart/setup_quickstart.html]

or adding a new page under Project Setup after IDE Setup?

> Extend quickstart docs on how to submit jobs
> 
>
> Key: FLINK-8654
> URL: https://issues.apache.org/jira/browse/FLINK-8654
> Project: Flink
>  Issue Type: Improvement
>  Components: Documentation, Quickstarts
>Affects Versions: 1.5.0
>Reporter: Chesnay Schepler
>Priority: Major
>
> The quickstart documentation explains how to setup the project, build the jar 
> and run things in the IDE, but neither explains how to submit the jar to a 
> cluster nor guides the user to where he could find this information (like the 
> CLI docs).
> Additionally, the quickstart poms should also contain the commands for 
> submitting the jar to a cluster, in particular how to select a main-class if 
> it wasn't set in the pom. (-c CLI flag)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9372) Typo on Elasticsearch website link (elastic.io --> elastic.co)

2018-05-15 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9372:
--

 Summary: Typo on Elasticsearch website link (elastic.io --> 
elastic.co)
 Key: FLINK-9372
 URL: https://issues.apache.org/jira/browse/FLINK-9372
 Project: Flink
  Issue Type: Improvement
  Components: Documentation, ElasticSearch Connector
Affects Versions: 1.4.2, 1.4.1, 1.5.0, 1.5.1
Reporter: Yazdan Shirvany
Assignee: Yazdan Shirvany


Typo on website link in Elasticsearch Java Docs (elastic.io --> elastic.co)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FLINK-1044) Website: Offer a zip archive with a pre-setup user project

2018-05-14 Thread Yazdan Shirvany (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474734#comment-16474734
 ] 

Yazdan Shirvany commented on FLINK-1044:


we might be able to use the outcome of this ticket also

FLINK-9008

which has this PR 

[https://github.com/apache/flink/pull/5823]

 

> Website: Offer a zip archive with a pre-setup user project
> --
>
> Key: FLINK-1044
> URL: https://issues.apache.org/jira/browse/FLINK-1044
> Project: Flink
>  Issue Type: Improvement
>  Components: Project Website
>Reporter: Stephan Ewen
>Priority: Minor
>  Labels: starter
> Attachments: flink-project.zip
>
>
> This is basically a shortcut for those that are not familiar with maven 
> archetypes or do not have maven installed (other then as part of the Eclipse 
> IDE or so).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (FLINK-1044) Website: Offer a zip archive with a pre-setup user project

2018-05-14 Thread Yazdan Shirvany (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474258#comment-16474258
 ] 

Yazdan Shirvany edited comment on FLINK-1044 at 5/14/18 7:52 PM:
-

[~StephanEwen]

here is a suggestion:
 * Create a submodule in the project (e.g., 
flink-examples/flink-sample-project) which using ${project.version} for basic 
flink dependencies
 * Build this submodule with all dependencies included in .jar
 * Add script to after_script in .travis.yml to push 
flink-examples/flink-sample-project/target/{{-.jar}}. 
file for this submodule to the S3 (or any other location that flink keeps this 
type of assets)
 * Point the document to this new artifact location via params coordinated with 
${projcet.version}

 

To make this work for each merged PR, we should  point this submodule to 
SnapShots repos 
([https://repository.apache.org/content/repositories/snapshots/])

or use local repository

mvn clean package -nsu 


was (Author: yazdanjs):
[~StephanEwen]

here is a suggestion:
 * Create a submodule in the project (e.g., 
flink-examples/flink-sample-project) which using ${project.version} for basic 
flink dependencies
 * Build this submodule with all dependencies included in .jar
 * Add script to after_script in .travis.yml to push 
flink-examples/flink-sample-project/target/{{-.jar}}. 
file for this submodule to the S3 (or any other location that flink keeps this 
type of assets)
 * Point the document to this new artifact location via params coordinated with 
${projcet.version}

 

To make this work for each merged PR, we should  point this submodule to 
SnapShots repos 
([https://repository.apache.org/content/repositories/snapshots/])

 

> Website: Offer a zip archive with a pre-setup user project
> --
>
> Key: FLINK-1044
> URL: https://issues.apache.org/jira/browse/FLINK-1044
> Project: Flink
>  Issue Type: Improvement
>  Components: Project Website
>Reporter: Stephan Ewen
>Priority: Minor
>  Labels: starter
> Attachments: flink-project.zip
>
>
> This is basically a shortcut for those that are not familiar with maven 
> archetypes or do not have maven installed (other then as part of the Eclipse 
> IDE or so).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (FLINK-1044) Website: Offer a zip archive with a pre-setup user project

2018-05-14 Thread Yazdan Shirvany (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474258#comment-16474258
 ] 

Yazdan Shirvany edited comment on FLINK-1044 at 5/14/18 7:21 PM:
-

[~StephanEwen]

here is a suggestion:
 * Create a submodule in the project (e.g., 
flink-examples/flink-sample-project) which using ${project.version} for basic 
flink dependencies
 * Build this submodule with all dependencies included in .jar
 * Add script to after_script in .travis.yml to push 
flink-examples/flink-sample-project/target/{{-.jar}}. 
file for this submodule to the S3 (or any other location that flink keeps this 
type of assets)
 * Point the document to this new artifact location via params coordinated with 
${projcet.version}

 

To make this work for each merged PR, we should  point this submodule to 
SnapShots repos 
([https://repository.apache.org/content/repositories/snapshots/])

 


was (Author: yazdanjs):
[~StephanEwen]

here is a suggestion:
 * Create a submodule in the project (e.g., 
flink-examples/flink-sample-project) which using ${project.version} for basic 
flink dependencies
 * Build this submodule with all dependencies included in .jar
 * Add script to after_script in .travis.yml to push 
flink-examples/flink-sample-project/target/*.jar file for this submodule to the 
S3 (or any other location that flink keeps this type of assets)
 * Point the document to this new artifact location via params coordinated with 
${projcet.version}

 

To make this work for each merged PR, we should  point this submodule to 
SnapShots repos (https://repository.apache.org/content/repositories/snapshots/)

 

> Website: Offer a zip archive with a pre-setup user project
> --
>
> Key: FLINK-1044
> URL: https://issues.apache.org/jira/browse/FLINK-1044
> Project: Flink
>  Issue Type: Improvement
>  Components: Project Website
>Reporter: Stephan Ewen
>Priority: Minor
>  Labels: starter
> Attachments: flink-project.zip
>
>
> This is basically a shortcut for those that are not familiar with maven 
> archetypes or do not have maven installed (other then as part of the Eclipse 
> IDE or so).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (FLINK-1044) Website: Offer a zip archive with a pre-setup user project

2018-05-14 Thread Yazdan Shirvany (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474258#comment-16474258
 ] 

Yazdan Shirvany edited comment on FLINK-1044 at 5/14/18 7:19 PM:
-

[~StephanEwen]

here is a suggestion:
 * Create a submodule in the project (e.g., 
flink-examples/flink-sample-project) which using ${project.version} for basic 
flink dependencies
 * Build this submodule with all dependencies included in .jar
 * Add script to after_script in .travis.yml to push 
flink-examples/flink-sample-project/target/*.jar file for this submodule to the 
S3 (or any other location that flink keeps this type of assets)
 * Point the document to this new artifact location via params coordinated with 
${projcet.version}

 

To make this work for each merged PR, we should  point this submodule to 
SnapShots repos (https://repository.apache.org/content/repositories/snapshots/)

 


was (Author: yazdanjs):
[~StephanEwen]

here is a suggestion:
 * Create a submodule in the project (e.g., 
flink-examples/flink-sample-project) which using ${project.version} for basic 
flink dependencies
 * Build this submodule with all dependencies included in .jar
 * Add script to after_script in .travis.yml to push 
flink-examples/flink-sample-project/target/*.jar file for this submodule to the 
S3 (or any other location that flink keeps this type of assets)
 * Point the document to this new artifact location via params coordinated with 
${projcet.version}

 

To make this work for each merged PR, we need to point this submodule to 
internal repos where the flink pushes packages after each build (if any)

There might be complexity in this approach also as I am not familiar with CICD 
pipeline for the project and what is the process to make this submodule package 
public facing.

 

> Website: Offer a zip archive with a pre-setup user project
> --
>
> Key: FLINK-1044
> URL: https://issues.apache.org/jira/browse/FLINK-1044
> Project: Flink
>  Issue Type: Improvement
>  Components: Project Website
>Reporter: Stephan Ewen
>Priority: Minor
>  Labels: starter
> Attachments: flink-project.zip
>
>
> This is basically a shortcut for those that are not familiar with maven 
> archetypes or do not have maven installed (other then as part of the Eclipse 
> IDE or so).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FLINK-9333) QuickStart Docs Spelling fix and some info regarding IntelliJ JVM Options

2018-05-14 Thread Yazdan Shirvany (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474512#comment-16474512
 ] 

Yazdan Shirvany commented on FLINK-9333:


[~Zentol] would you please review this.

> QuickStart Docs Spelling fix and some info regarding IntelliJ JVM Options
> -
>
> Key: FLINK-9333
> URL: https://issues.apache.org/jira/browse/FLINK-9333
> Project: Flink
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.4.1, 1.4.2
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Trivial
>  Labels: document, spelling
>
> - Spelling fix for QuickStart Project Template for Java 
> - Adding more details regarding changing JVM options in IntelliJ IDEA



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FLINK-9348) scalastyle documentation for IntelliJ IDE setup

2018-05-14 Thread Yazdan Shirvany (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474506#comment-16474506
 ] 

Yazdan Shirvany commented on FLINK-9348:


master: 

d82fbf4529146b38d929a3c31a767843fed3d64e

1.5: 23975b4a1833a4935da559d761b1e9a2d1a7418a

> scalastyle documentation for IntelliJ IDE setup
> ---
>
> Key: FLINK-9348
> URL: https://issues.apache.org/jira/browse/FLINK-9348
> Project: Flink
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.4.1, 1.4.2
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Trivial
>
> Documentation regarding enabling scalastyle for IntelliJ IDEA Setup in 
> contribution page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (FLINK-9348) scalastyle documentation for IntelliJ IDE setup

2018-05-14 Thread Yazdan Shirvany (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany closed FLINK-9348.
--

> scalastyle documentation for IntelliJ IDE setup
> ---
>
> Key: FLINK-9348
> URL: https://issues.apache.org/jira/browse/FLINK-9348
> Project: Flink
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.4.1, 1.4.2
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Trivial
>
> Documentation regarding enabling scalastyle for IntelliJ IDEA Setup in 
> contribution page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FLINK-9348) scalastyle documentation for IntelliJ IDE setup

2018-05-14 Thread Yazdan Shirvany (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany resolved FLINK-9348.

Resolution: Fixed

> scalastyle documentation for IntelliJ IDE setup
> ---
>
> Key: FLINK-9348
> URL: https://issues.apache.org/jira/browse/FLINK-9348
> Project: Flink
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.4.1, 1.4.2
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Trivial
>
> Documentation regarding enabling scalastyle for IntelliJ IDEA Setup in 
> contribution page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FLINK-1044) Website: Offer a zip archive with a pre-setup user project

2018-05-14 Thread Yazdan Shirvany (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474258#comment-16474258
 ] 

Yazdan Shirvany commented on FLINK-1044:


[~StephanEwen]

here is a suggestion:
 * Create a submodule in the project (e.g., 
flink-examples/flink-sample-project) which using ${project.version} for basic 
flink dependencies
 * Build this submodule with all dependencies included in .jar
 * Add script to after_script in .travis.yml to push 
flink-examples/flink-sample-project/target/*.jar file for this submodule to the 
S3 (or any other location that flink keeps this type of assets)
 * Point the document to this new artifact location via params coordinated with 
${projcet.version}

 

To make this work for each merged PR, we need to point this submodule to 
internal repos where the flink pushes packages after each build (if any)

There might be complexity in this approach also as I am not familiar with CICD 
pipeline for the project and what is the process to make this submodule package 
public facing.

 

> Website: Offer a zip archive with a pre-setup user project
> --
>
> Key: FLINK-1044
> URL: https://issues.apache.org/jira/browse/FLINK-1044
> Project: Flink
>  Issue Type: Improvement
>  Components: Project Website
>Reporter: Stephan Ewen
>Priority: Minor
>  Labels: starter
> Attachments: flink-project.zip
>
>
> This is basically a shortcut for those that are not familiar with maven 
> archetypes or do not have maven installed (other then as part of the Eclipse 
> IDE or so).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (FLINK-9333) QuickStart Docs Spelling fix and some info regarding IntelliJ JVM Options

2018-05-13 Thread Yazdan Shirvany (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany reassigned FLINK-9333:
--

Assignee: Yazdan Shirvany

> QuickStart Docs Spelling fix and some info regarding IntelliJ JVM Options
> -
>
> Key: FLINK-9333
> URL: https://issues.apache.org/jira/browse/FLINK-9333
> Project: Flink
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.4.1, 1.4.2
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Trivial
>  Labels: document, spelling
>
> - Spelling fix for QuickStart Project Template for Java 
> - Adding more details regarding changing JVM options in IntelliJ IDEA



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (FLINK-9343) Add Async Example with External Rest API call

2018-05-13 Thread Yazdan Shirvany (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-9343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany reassigned FLINK-9343:
--

Assignee: Yazdan Shirvany

> Add Async Example with External Rest API call
> -
>
> Key: FLINK-9343
> URL: https://issues.apache.org/jira/browse/FLINK-9343
> Project: Flink
>  Issue Type: Improvement
>  Components: Examples
>Affects Versions: 1.4.0, 1.4.1, 1.4.2
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Minor
>
> Async I/O is a good way to call External resources such as REST API and 
> enrich the stream with external data.
> Adding example to simulate Async GET api call on an input stream.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (FLINK-9348) scalastyle documentation for IntelliJ IDE setup

2018-05-13 Thread Yazdan Shirvany (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany reassigned FLINK-9348:
--

Assignee: Yazdan Shirvany

> scalastyle documentation for IntelliJ IDE setup
> ---
>
> Key: FLINK-9348
> URL: https://issues.apache.org/jira/browse/FLINK-9348
> Project: Flink
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.4.1, 1.4.2
>Reporter: Yazdan Shirvany
>Assignee: Yazdan Shirvany
>Priority: Trivial
>
> Documentation regarding enabling scalastyle for IntelliJ IDEA Setup in 
> contribution page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FLINK-9299) ProcessWindowFunction documentation Java examples have errors

2018-05-13 Thread Yazdan Shirvany (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-9299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473489#comment-16473489
 ] 

Yazdan Shirvany commented on FLINK-9299:


[~yanghua] Thanks for the fix. Will keep in mind to ask before starting the 
work :)

I will close my PR as yours addressed all of the issues.

> ProcessWindowFunction documentation Java examples have errors
> -
>
> Key: FLINK-9299
> URL: https://issues.apache.org/jira/browse/FLINK-9299
> Project: Flink
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.4.2
>Reporter: Ken Krugler
>Assignee: vinoyang
>Priority: Minor
>
> In looking at 
> [https://ci.apache.org/projects/flink/flink-docs-release-1.4/dev/stream/operators/windows.html#processwindowfunction-with-incremental-aggregation],
>  I noticed a few errors...
>  * "This allows to incrementally compute windows" should be "This allows it 
> to incrementally compute windows"
>  * DataStream input = ...; should be 
> DataStream> input = ...;
>  * The getResult() method needs to cast one of the accumulator values to a 
> double, if that's what it is going to return.
>  * MyProcessWindowFunction needs to extend, not implement 
> ProcessWindowFunction
>  * MyProcessWindowFunction needs to implement a process() method, not an 
> apply() method.
>  * The call to .timeWindow takes a Time parameter, not a window assigner.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FLINK-9299) ProcessWindowFunction documentation Java examples have errors

2018-05-12 Thread Yazdan Shirvany (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-9299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473376#comment-16473376
 ] 

Yazdan Shirvany commented on FLINK-9299:


[~yanghua] please review and assign this to myself 

> ProcessWindowFunction documentation Java examples have errors
> -
>
> Key: FLINK-9299
> URL: https://issues.apache.org/jira/browse/FLINK-9299
> Project: Flink
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.4.2
>Reporter: Ken Krugler
>Assignee: vinoyang
>Priority: Minor
>
> In looking at 
> [https://ci.apache.org/projects/flink/flink-docs-release-1.4/dev/stream/operators/windows.html#processwindowfunction-with-incremental-aggregation],
>  I noticed a few errors...
>  * "This allows to incrementally compute windows" should be "This allows it 
> to incrementally compute windows"
>  * DataStream input = ...; should be 
> DataStream> input = ...;
>  * The getResult() method needs to cast one of the accumulator values to a 
> double, if that's what it is going to return.
>  * MyProcessWindowFunction needs to extend, not implement 
> ProcessWindowFunction
>  * MyProcessWindowFunction needs to implement a process() method, not an 
> apply() method.
>  * The call to .timeWindow takes a Time parameter, not a window assigner.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9348) scalastyle documentation for IntelliJ IDE setup

2018-05-12 Thread Yazdan Shirvany (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9348:
---
Summary: scalastyle documentation for IntelliJ IDE setup  (was: scalastyle 
documentatiom for IntelliJ IDE setup)

> scalastyle documentation for IntelliJ IDE setup
> ---
>
> Key: FLINK-9348
> URL: https://issues.apache.org/jira/browse/FLINK-9348
> Project: Flink
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.4.1, 1.4.2
>Reporter: Yazdan Shirvany
>Priority: Trivial
>
> Documentation regarding enabling scalastyle for IntelliJ IDEA Setup in 
> contribution page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9348) scalastyle documentatiom for IntelliJ IDE setup

2018-05-12 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9348:
--

 Summary: scalastyle documentatiom for IntelliJ IDE setup
 Key: FLINK-9348
 URL: https://issues.apache.org/jira/browse/FLINK-9348
 Project: Flink
  Issue Type: Bug
  Components: Documentation
Affects Versions: 1.4.2, 1.4.1
Reporter: Yazdan Shirvany


Documentation regarding enabling scalastyle for IntelliJ IDEA Setup in 
contribution page



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9343) Add Async Example with External Rest API call

2018-05-11 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9343:
--

 Summary: Add Async Example with External Rest API call
 Key: FLINK-9343
 URL: https://issues.apache.org/jira/browse/FLINK-9343
 Project: Flink
  Issue Type: Improvement
  Components: Examples
Affects Versions: 1.4.2, 1.4.1, 1.4.0
Reporter: Yazdan Shirvany


Async I/O is a good way to call External resources such as REST API and enrich 
the stream with external data.

Adding example to simulate Async GET api call on an input stream.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FLINK-1044) Website: Offer a zip archive with a pre-setup user project

2018-05-11 Thread Yazdan Shirvany (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472552#comment-16472552
 ] 

Yazdan Shirvany commented on FLINK-1044:


This looks old but still useful for someone who work behind proxy and can't 
build the code via mvn/sbt. If still needed I can pick it up and put the fix in 
and update the documentaions

> Website: Offer a zip archive with a pre-setup user project
> --
>
> Key: FLINK-1044
> URL: https://issues.apache.org/jira/browse/FLINK-1044
> Project: Flink
>  Issue Type: Improvement
>  Components: Project Website
>Reporter: Stephan Ewen
>Priority: Minor
>  Labels: starter
> Attachments: flink-project.zip
>
>
> This is basically a shortcut for those that are not familiar with maven 
> archetypes or do not have maven installed (other then as part of the Eclipse 
> IDE or so).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9333) QuickStart Docs Spelling fix and some info regarding IntelliJ JVM Options

2018-05-11 Thread Yazdan Shirvany (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9333:
---
Labels: document  (was: )

> QuickStart Docs Spelling fix and some info regarding IntelliJ JVM Options
> -
>
> Key: FLINK-9333
> URL: https://issues.apache.org/jira/browse/FLINK-9333
> Project: Flink
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.4.1, 1.4.2
>Reporter: Yazdan Shirvany
>Priority: Trivial
>  Labels: document, spelling
>
> - Spelling fix for QuickStart Project Template for Java 
> - Adding more details regarding changing JVM options in IntelliJ IDEA



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9333) QuickStart Docs Spelling fix and some info regarding IntelliJ JVM Options

2018-05-11 Thread Yazdan Shirvany (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9333:
---
Labels: document spelling  (was: document)

> QuickStart Docs Spelling fix and some info regarding IntelliJ JVM Options
> -
>
> Key: FLINK-9333
> URL: https://issues.apache.org/jira/browse/FLINK-9333
> Project: Flink
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.4.1, 1.4.2
>Reporter: Yazdan Shirvany
>Priority: Trivial
>  Labels: document, spelling
>
> - Spelling fix for QuickStart Project Template for Java 
> - Adding more details regarding changing JVM options in IntelliJ IDEA



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9333) QuickStart Docs Spelling fix and some info regarding IntelliJ JVM Options

2018-05-10 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9333:
--

 Summary: QuickStart Docs Spelling fix and some info regarding 
IntelliJ JVM Options
 Key: FLINK-9333
 URL: https://issues.apache.org/jira/browse/FLINK-9333
 Project: Flink
  Issue Type: Bug
  Components: Documentation
Affects Versions: 1.4.2, 1.4.1
Reporter: Yazdan Shirvany


- Spelling fix for QuickStart Project Template for Java 

- Adding more details regarding changing JVM options in IntelliJ IDEA



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-9317) Async I/O API Example For Scala has Variable Name error

2018-05-08 Thread Yazdan Shirvany (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-9317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yazdan Shirvany updated FLINK-9317:
---
Description: 
h2. Async I/O API Scala Example has duplicated {{resultFuture variable with 
different data type.}}

 

{{resultFuture: ResultFuture[(String, String)]}}

val resultFuture: Future[String]

 

{{this cause error on compile as variables have same naming.}}

 

{{In order to example works properly we need to update variable names to be 
distinct,}}

 

{{```}}

override def asyncInvoke(input: (String,String, String), resultFuture: 
ResultFuture[(String,String, String, String)]): Unit = {

// issue the asynchronous request, receive a future for the result
 val *resultFutureRequested*: Future[String] = Future

{ // client2.query(str) client.getAccountReferenceId(token, input._1) }

// set the callback to be executed once the request by the client is complete
 // the callback simply forwards the result to the result future
 *resultFutureRequested*.onSuccess {
 case result: String =>

{ resultFuture.complete(Iterable((input._1, input._2, input._3, result))) }

}
 }

{{```}}

 

 

  was:
h2. Async I/O API Scala Example has duplicated {{resultFuture variable with 
different data type.}}

 

{{resultFuture: ResultFuture[(String, String)]}}

{{ val resultFuture: Future[String]}}

 

{{this cause error on compile as variables have same naming.}}

 

{{In order to example works properly we need to update variable names to be 
distinct,}}

 

{{```}}

override def asyncInvoke(input: (String,String, String), resultFuture: 
ResultFuture[(String,String, String, String)]): Unit = {


 // issue the asynchronous request, receive a future for the result
 val *resultFutureRequested*: Future[String] = Future {
 // client2.query(str)
 client.getAccountReferenceId(token, input._1)
 }

 // set the callback to be executed once the request by the client is complete
 // the callback simply forwards the result to the result future
 *resultFutureRequested*.onSuccess {
 case result: String => {
 resultFuture.complete(Iterable((input._1, input._2, input._3, result)))
 }
 }
}

{{```}}

 

 


> Async I/O API Example For Scala has Variable Name error
> ---
>
> Key: FLINK-9317
> URL: https://issues.apache.org/jira/browse/FLINK-9317
> Project: Flink
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.4.1, 1.4.2
>Reporter: Yazdan Shirvany
>Priority: Minor
>  Labels: documentation
>
> h2. Async I/O API Scala Example has duplicated {{resultFuture variable with 
> different data type.}}
>  
> {{resultFuture: ResultFuture[(String, String)]}}
> val resultFuture: Future[String]
>  
> {{this cause error on compile as variables have same naming.}}
>  
> {{In order to example works properly we need to update variable names to be 
> distinct,}}
>  
> {{```}}
> override def asyncInvoke(input: (String,String, String), resultFuture: 
> ResultFuture[(String,String, String, String)]): Unit = {
> // issue the asynchronous request, receive a future for the result
>  val *resultFutureRequested*: Future[String] = Future
> { // client2.query(str) client.getAccountReferenceId(token, input._1) }
> // set the callback to be executed once the request by the client is complete
>  // the callback simply forwards the result to the result future
>  *resultFutureRequested*.onSuccess {
>  case result: String =>
> { resultFuture.complete(Iterable((input._1, input._2, input._3, result))) }
> }
>  }
> {{```}}
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9317) Async I/O API Example For Scala has Variable Name error

2018-05-08 Thread Yazdan Shirvany (JIRA)
Yazdan Shirvany created FLINK-9317:
--

 Summary: Async I/O API Example For Scala has Variable Name error
 Key: FLINK-9317
 URL: https://issues.apache.org/jira/browse/FLINK-9317
 Project: Flink
  Issue Type: Bug
  Components: Documentation
Affects Versions: 1.4.2, 1.4.1
Reporter: Yazdan Shirvany


h2. Async I/O API Scala Example has duplicated {{resultFuture variable with 
different data type.}}

 

{{resultFuture: ResultFuture[(String, String)]}}

{{ val resultFuture: Future[String]}}

 

{{this cause error on compile as variables have same naming.}}

 

{{In order to example works properly we need to update variable names to be 
distinct,}}

 

{{```}}

override def asyncInvoke(input: (String,String, String), resultFuture: 
ResultFuture[(String,String, String, String)]): Unit = {


 // issue the asynchronous request, receive a future for the result
 val *resultFutureRequested*: Future[String] = Future {
 // client2.query(str)
 client.getAccountReferenceId(token, input._1)
 }

 // set the callback to be executed once the request by the client is complete
 // the callback simply forwards the result to the result future
 *resultFutureRequested*.onSuccess {
 case result: String => {
 resultFuture.complete(Iterable((input._1, input._2, input._3, result)))
 }
 }
}

{{```}}

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)