[jira] [Updated] (FLINK-2044) Implementation of Gelly HITS Algorithm

[Vasia Kalavri (JIRA)]

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

Vasia Kalavri updated FLINK-2044:
-
Issue Type: New Feature  (was: Improvement)

> Implementation of Gelly HITS Algorithm
> --
>
> Key: FLINK-2044
> URL: https://issues.apache.org/jira/browse/FLINK-2044
> Project: Flink
>  Issue Type: New Feature
>  Components: Gelly
>Reporter: Ahamd Javid
>Priority: Minor
>
> Implementation of Hits Algorithm in Gelly API using Java. the feature branch 
> can be found here: (https://github.com/JavidMayar/flink/commits/HITS)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (FLINK-3000) Add ShutdownHook to YARN CLI to prevent lingering sessions

[Sachin Goel (JIRA)]

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

Sachin Goel reassigned FLINK-3000:
--

Assignee: Sachin Goel

> Add ShutdownHook to YARN CLI to prevent lingering sessions
> --
>
> Key: FLINK-3000
> URL: https://issues.apache.org/jira/browse/FLINK-3000
> Project: Flink
>  Issue Type: Bug
>  Components: YARN Client
>Affects Versions: 0.10
>Reporter: Ufuk Celebi
>Assignee: Sachin Goel
> Fix For: 0.10.1
>
>
> Submitting a job via
> {code}
> bin/flink run -m yarn-cluster ...
> {code}
> and terminating the client can lead to lingering YARN sessions allocating 
> cluster resources.
> This was reported by a user.
> {code}
> 1) One starts a flink job in the yarn mode
> 2) He sees that containers are not allocated since cluster is busy
> 3) Presses Ctrl+C
> 4) An “empty” flink session remains in the cluster although the Flink didn’t 
> print that “you can track your application on the X URL”
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FLINK-3002) Add an EitherType to the Java API

[Vasia Kalavri (JIRA)]

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

Vasia Kalavri commented on FLINK-3002:
--

Here's my first take on this: 
https://github.com/vasia/flink/tree/either-java-type.
I created an Either class with an empty constructor and 2 static methods to 
create Left and Right. I also have an initial implementation for the 
EitherTypeInfo and EitherSerializer. Feedback and ideas are welcome! If you 
think that's a nice way to go, I'll clean up the code and write tests. In my 
view, the problem with Either not being abstract is semantic, i.e. an Either 
that is neither Left nor Right shouldn't be allowed.


> Add an EitherType to the Java API
> -
>
> Key: FLINK-3002
> URL: https://issues.apache.org/jira/browse/FLINK-3002
> Project: Flink
>  Issue Type: New Feature
>  Components: Java API
>Affects Versions: 0.10
>Reporter: Stephan Ewen
>Assignee: Vasia Kalavri
> Fix For: 1.0
>
>
> Either types are recurring patterns and should be serialized efficiently, so 
> it makes sense to add them to the core Java API.
> Since Java does not have such a type as of Java 8, we would need to add our 
> own version.
> The Scala API handles the Scala Either Type already efficiently. I would not 
> use the Scala Either Type in the Java API, since we are trying to get the 
> {{flink-java}} project "Scala free" for people that don't use Scala and o not 
> want to worry about Scala version matches and mismatches.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] flink pull request: [FLINK-3000]Adds shutdown hook to clean up lin...

[sachingoel0101]

GitHub user sachingoel0101 opened a pull request:

https://github.com/apache/flink/pull/1354

[FLINK-3000]Adds shutdown hook to clean up lingering yarn sessions

Adds a shutdown hook to cleanup the submitted yarn application while the 
user cancels it in any but a `RUNNING` state. If running, there are two cases: 
Detached and Non-detached. Non detached modes will connect to the cluster and 
add a shut down hook, while detached ones, well, since they're detached, once 
deployed, users have to cancel them explicitly.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sachingoel0101/flink yarn_cli

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/flink/pull/1354.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1354


commit e1b8778491bf8fd592bddc8fe157d8aa8c150b7f
Author: Sachin Goel 
Date:   2015-11-15T00:41:30Z

Adds shutdown hook to clean up lingering yarn sessions




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (FLINK-3000) Add ShutdownHook to YARN CLI to prevent lingering sessions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on FLINK-3000:
---

GitHub user sachingoel0101 opened a pull request:

https://github.com/apache/flink/pull/1354

[FLINK-3000]Adds shutdown hook to clean up lingering yarn sessions

Adds a shutdown hook to cleanup the submitted yarn application while the 
user cancels it in any but a `RUNNING` state. If running, there are two cases: 
Detached and Non-detached. Non detached modes will connect to the cluster and 
add a shut down hook, while detached ones, well, since they're detached, once 
deployed, users have to cancel them explicitly.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sachingoel0101/flink yarn_cli

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/flink/pull/1354.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1354


commit e1b8778491bf8fd592bddc8fe157d8aa8c150b7f
Author: Sachin Goel 
Date:   2015-11-15T00:41:30Z

Adds shutdown hook to clean up lingering yarn sessions




> Add ShutdownHook to YARN CLI to prevent lingering sessions
> --
>
> Key: FLINK-3000
> URL: https://issues.apache.org/jira/browse/FLINK-3000
> Project: Flink
>  Issue Type: Bug
>  Components: YARN Client
>Affects Versions: 0.10
>Reporter: Ufuk Celebi
>Assignee: Sachin Goel
> Fix For: 0.10.1
>
>
> Submitting a job via
> {code}
> bin/flink run -m yarn-cluster ...
> {code}
> and terminating the client can lead to lingering YARN sessions allocating 
> cluster resources.
> This was reported by a user.
> {code}
> 1) One starts a flink job in the yarn mode
> 2) He sees that containers are not allocated since cluster is busy
> 3) Presses Ctrl+C
> 4) An “empty” flink session remains in the cluster although the Flink didn’t 
> print that “you can track your application on the X URL”
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)