[
https://issues.apache.org/jira/browse/APEXMALHAR-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Yan resolved APEXMALHAR-2112.
---
Resolution: Fixed
> Contrib tests are failing because of inclusion of apache logger with
Github user asfgit closed the pull request at:
https://github.com/apache/apex-malhar/pull/312
---
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
[
https://issues.apache.org/jira/browse/APEXCORE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise closed APEXCORE-442.
-
Resolution: Fixed
> Remove "incubation" and its variants from our code base
>
Github user asfgit closed the pull request at:
https://github.com/apache/apex-site/pull/35
---
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
[
https://issues.apache.org/jira/browse/APEXCORE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15315201#comment-15315201
]
ASF GitHub Bot commented on APEXCORE-442:
-
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/apex-core/pull/317
---
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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15315198#comment-15315198
]
ASF GitHub Bot commented on APEXMALHAR-2112:
GitHub user chinmaykolhatkar opened a pull
Github user tweise commented on the issue:
https://github.com/apache/apex-core/pull/317
@davidyan74 pushed the change, mirror does not pick it up yet.
---
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
[
https://issues.apache.org/jira/browse/APEXCORE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15315187#comment-15315187
]
ASF GitHub Bot commented on APEXCORE-466:
-
Github user davidyan74 commented on a diff in the
Github user davidyan74 commented on a diff in the pull request:
https://github.com/apache/apex-core/pull/339#discussion_r65793703
--- Diff:
engine/src/main/java/com/datatorrent/stram/client/RecordingsAgent.java ---
@@ -640,7 +640,7 @@ public JSONObject process(WebResource.Builder
The following will update your remotes automatically. Go to the root of
the repository you need to update from incubator to top level and execute:
for remote in `git remote`; do new_url=`git config --get remote.$remote.url
| sed 's|incubator-||'`; echo $remote $new_url; git remote set-url
[
https://issues.apache.org/jira/browse/APEXCORE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15315174#comment-15315174
]
ASF GitHub Bot commented on APEXCORE-442:
-
Github user tweise commented on a diff in the pull
Github user tweise commented on a diff in the pull request:
https://github.com/apache/apex-site/pull/35#discussion_r65793171
--- Diff: gulpfile.js ---
@@ -297,16 +297,15 @@ gulp.task('fetch-releases', function(taskCb) {
// The release "targets", in this case meaning
[
https://issues.apache.org/jira/browse/APEXCORE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15315171#comment-15315171
]
ASF GitHub Bot commented on APEXCORE-442:
-
Github user tweise commented on a diff in the pull
Github user tweise commented on a diff in the pull request:
https://github.com/apache/apex-site/pull/35#discussion_r65793037
--- Diff: src/pages/downloads.html ---
@@ -28,22 +28,22 @@
{{releaseDate version.date}}
-
[
https://issues.apache.org/jira/browse/APEXCORE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15315141#comment-15315141
]
ASF GitHub Bot commented on APEXCORE-442:
-
Github user davidyan74 commented on the issue:
Github user davidyan74 commented on the issue:
https://github.com/apache/apex-core/pull/317
@tweise please merge
---
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
The ASF git repos are done, github mirrors should follow shortly.
You may need to change your remotes and mirroring may be interrupted for a
while.
Thanks,
Thomas
Hey no worries Sunil. Seems like the application master killed the
containers for the operator because it might not have received the
heartbeats for some time. This typically happens if the windows are not
moving forward in the container. Can you check the app master logs if the
heartbeats are
[
https://issues.apache.org/jira/browse/APEXMALHAR-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15315068#comment-15315068
]
ASF GitHub Bot commented on APEXMALHAR-1957:
Github user bhupeshchawda commented on a
[
https://issues.apache.org/jira/browse/APEXMALHAR-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15315066#comment-15315066
]
ASF GitHub Bot commented on APEXMALHAR-1957:
Github user bhupeshchawda commented on a
Github user bhupeshchawda commented on a diff in the pull request:
https://github.com/apache/incubator-apex-malhar/pull/292#discussion_r65787947
--- Diff:
contrib/src/main/java/com/datatorrent/contrib/hbase/HBasePOJOInputOperator.java
---
@@ -69,116 +70,105 @@ public Object
[
https://issues.apache.org/jira/browse/APEXMALHAR-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15315053#comment-15315053
]
ASF GitHub Bot commented on APEXMALHAR-1957:
Github user bhupeshchawda commented on a
[
https://issues.apache.org/jira/browse/APEXMALHAR-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314820#comment-15314820
]
Chandni Singh commented on APEXMALHAR-2063:
---
Embedding the window id into the WAL was not
[
https://issues.apache.org/jira/browse/APEXMALHAR-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314788#comment-15314788
]
ASF GitHub Bot commented on APEXMALHAR-2104:
Github user PramodSSImmaneni commented on a
[
https://issues.apache.org/jira/browse/APEXMALHAR-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314764#comment-15314764
]
Thomas Weise commented on APEXMALHAR-2063:
--
Small files problem but also extra name node
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-apex-malhar/pull/304
---
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
[
https://issues.apache.org/jira/browse/APEXMALHAR-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314744#comment-15314744
]
ASF GitHub Bot commented on APEXMALHAR-2104:
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/APEXMALHAR-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314680#comment-15314680
]
Chandni Singh commented on APEXMALHAR-2063:
---
I am looking into the possibility of writing
The 3.4.0 release isn't backward compatible due to the security related
change in core. So this was an opportunity to clean up this confusion also.
You are right that since this operator wasn't evolving, we should have
listed it in the release notes.
--
sent from mobile
On Jun 3, 2016 7:11 AM,
Hi All,
We had developed an application using AbstractKafkaInputOperator from
Malhar 3.2.0-incubator. We are planning to upgrade to Malhar 3.4.0. While
recompiling our code, we observed that the compilation fails due to
backward incompatible change in the AbstractKafkaInputOperator. The
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-apex-core/pull/338
---
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
32 matches
Mail list logo
