[jira] [Commented] (APEXCORE-649) Infrastructure for user define stram event listeners.

2017-04-21 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15979542#comment-15979542 ] ASF GitHub Bot commented on APEXCORE-649: - Github user asfgit closed the pull re

[GitHub] apex-core pull request #503: APEXCORE-649 Provide snapshot of DAG to plugins...

2017-04-21 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/apex-core/pull/503 --- 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 e

[jira] [Updated] (APEXCORE-699) Investigate versioning for plugins

2017-04-21 Thread Vlad Rozov (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-699: Fix Version/s: (was: 3.6.0) > Investigate versioning for plugins > ---

[jira] [Resolved] (APEXCORE-709) Refactor changes done through APEXCORE-575

2017-04-21 Thread Vlad Rozov (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov resolved APEXCORE-709. - Resolution: Fixed > Refactor changes done through APEXCORE-575 > ---

[jira] [Commented] (APEXCORE-709) Refactor changes done through APEXCORE-575

2017-04-21 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/APEXCORE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978789#comment-15978789 ] ASF GitHub Bot commented on APEXCORE-709: - Github user asfgit closed the pull re

[GitHub] apex-core pull request #517: APEXCORE-709 Refactor code chagnes made through...

2017-04-21 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/apex-core/pull/517 --- 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 e

Re: Enhancement to support custom SSL configuration

2017-04-21 Thread Aniruddha Thombare
+1 for custom keystore support. Thanks, Aniruddha _ Always finding your faults, just like your Mom! #QA On Fri, Apr 21, 2017 at 12:47 PM, Sanjay Pujare wrote: > Regarding distributing the SSL files by us, I agree it is not ideal because > we are t

Re: Enhancement to support custom SSL configuration

2017-04-21 Thread Sanjay Pujare
Regarding distributing the SSL files by us, I agree it is not ideal because we are taking the responsibility of distributing sensitive security material. But it would also be very convenient for certain users. Also as some users have pointed out there is a precedent: H2O does it as per http://docs.

Re: Enhancement to support custom SSL configuration

2017-04-21 Thread Priyanka Gugale
+1 for this support, it's important to let users use their own own keystore files. Is it okay to distribute files inside our package along with jar/resources, are there any security restrictions? Or we should use other medium like HDFS or other shared file system to host these key files? -Priyank

Enhancement to support custom SSL configuration

2017-04-21 Thread Sanjay Pujare
Currently StrAM supports only the default Hadoop SSL configuration because it uses org.apache.hadoop.yarn.webapp.WebApps helper class which has the limitation of only using the default Hadoop SSL config that is read from Hadoop's ssl-server.xml resource file. Some users have run into a situation wh