+1 for proposal.
Can we make new behaviour of writing to users own directory as default?
Most probably users will upgrade gateway with apex-core. If not, they
always have option to set the flag and fall back to legacy behaviour.
-Priyanka
On Fri, May 19, 2017 at 7:52 AM, Chinmay Kolhatkar
wrote
[
https://issues.apache.org/jira/browse/APEXCORE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016862#comment-16016862
]
Deepak Narkhede commented on APEXCORE-724:
--
Hi Thomas,
I would like to contrib
Thomas Weise created APEXCORE-724:
-
Summary: Support for Kubernetes
Key: APEXCORE-724
URL: https://issues.apache.org/jira/browse/APEXCORE-724
Project: Apache Apex Core
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/APEXMALHAR-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXMALHAR-2495:
-
Labels: roadmap (was: )
> Apex SQL: Add support for windowing
>
[
https://issues.apache.org/jira/browse/APEXMALHAR-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXMALHAR-2296:
-
Labels: (was: roadmap)
> Apex SQL: Add support for SQL GROUP BY (Aggregate RelNode)
[
https://issues.apache.org/jira/browse/APEXMALHAR-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXMALHAR-2296:
-
Labels: roadmap (was: )
> Apex SQL: Add support for SQL GROUP BY (Aggregate RelNode)
Thomas Weise created APEXMALHAR-2495:
Summary: Apex SQL: Add support for windowing
Key: APEXMALHAR-2495
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2495
Project: Apache Apex Malhar
[
https://issues.apache.org/jira/browse/APEXCORE-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise closed APEXCORE-721.
-
Resolution: Done
> Announcement section on the website is not uptodate
> ---
Github user asfgit closed the pull request at:
https://github.com/apache/apex-site/pull/75
---
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 en
[
https://issues.apache.org/jira/browse/APEXCORE-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016809#comment-16016809
]
ASF GitHub Bot commented on APEXCORE-721:
-
Github user asfgit closed the pull re
+1 for pramod's proposal.
On 19-May-2017 4:51 AM, "Sanjay Pujare" wrote:
> +1 for Pramod's proposal for impersonation.
>
> I have an issue with Sandesh's suggestion about making the new behavior as
> the default (or only) behavior. This will introduce incompatibility with
> other legacy tools (e
+1 for Pramod's proposal for impersonation.
I have an issue with Sandesh's suggestion about making the new behavior as
the default (or only) behavior. This will introduce incompatibility with
other legacy tools (e.g. Datatorrent's dtGateway) that assume user A's HDFS
path as the application path.
My vote is to make the new proposal as the default behavior. Is there a use
case for the current behavior? If not then no need to add the configuration
setting.
On Thu, May 18, 2017 at 3:47 PM Pramod Immaneni
wrote:
> Sorry typo in sentence "as we are not asking for permissions for a lower
> pri
Sorry typo in sentence "as we are not asking for permissions for a lower
privilege", please read as "as we are now asking for permissions for a
lower privilege".
On Thu, May 18, 2017 at 3:44 PM, Pramod Immaneni
wrote:
> Apex cli supports impersonation in secure mode. With impersonation, the
> us
Apex cli supports impersonation in secure mode. With impersonation, the
user running the cli or the user authenticating with hadoop (henceforth
referred to as login user) can be different from the effective user with
which the actions are performed under hadoop. An example for this is an
applicatio
Github user prasannapramod closed the pull request at:
https://github.com/apache/apex-malhar/pull/604
---
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 fe
GitHub user prasannapramod reopened a pull request:
https://github.com/apache/apex-malhar/pull/604
Apexmalhar 2467 Move JMS related examples from datatorrent examples to
apex-malhar examples
@amberarrow @tweise @ashwinchandrap please review
You can merge this pull request into a Gi
[
https://issues.apache.org/jira/browse/APEXMALHAR-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni resolved APEXMALHAR-2475.
-
Resolution: Fixed
Fix Version/s: 3.8.0
> CacheStore needn't expire dat
[
https://issues.apache.org/jira/browse/APEXMALHAR-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni resolved APEXMALHAR-2474.
-
Resolution: Fixed
Fix Version/s: 3.8.0
> FSLoader only returns value a
[
https://issues.apache.org/jira/browse/APEXMALHAR-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pramod Immaneni resolved APEXMALHAR-2473.
-
Resolution: Fixed
Fix Version/s: 3.8.0
> Support for global cache meta
[
https://issues.apache.org/jira/browse/APEXMALHAR-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016435#comment-16016435
]
ASF GitHub Bot commented on APEXMALHAR-2473:
Github user asfgit closed th
Github user asfgit closed the pull request at:
https://github.com/apache/apex-malhar/pull/605
---
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
Chaitanya created APEXMALHAR-2494:
-
Summary: Update demo apps with description
Key: APEXMALHAR-2494
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2494
Project: Apache Apex Malhar
Issu
[
https://issues.apache.org/jira/browse/APEXMALHAR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015556#comment-16015556
]
ASF GitHub Bot commented on APEXMALHAR-2493:
GitHub user chaithu14 opened
GitHub user chaithu14 opened a pull request:
https://github.com/apache/apex-malhar/pull/622
APEXMALHAR-2493 Fixed the issue of KafkaSinglePortExactlyOnceOutputOperator
going to the blocked state during recovery
@sandeshh @tushargosavi Please review and merge.
You can merge this pul
Chaitanya created APEXMALHAR-2493:
-
Summary: KafkaSinglePortExactlyOnceOutputOperator going to the
blocked state during recovery
Key: APEXMALHAR-2493
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2493
26 matches
Mail list logo
