+1 for the change.
At some point in time, user'll need this to specify fields related to time
more meaningfully.
On Wed, May 4, 2016 at 10:17 AM, Sandeep Deshmukh
wrote:
> +1.
> Good to have intuitive way of using fields.
>
> Regards,
> Sandeep
>
> On Wed, May 4, 2016 at 9:39 AM, Shubham Pathak
+1
Regards,
Sandeep
On Fri, Apr 29, 2016 at 3:26 PM, Mohit Jotwani
wrote:
> +1
>
> Regards,
> Mohit
>
> On Fri, Apr 29, 2016 at 2:09 PM, Chaitanya Chebolu <
> chaita...@datatorrent.com> wrote:
>
> > Hi All,
> >
> > I am proposing NFS Input Module. Use case is to read large files from
> NFS
>
+1.
Good to have intuitive way of using fields.
Regards,
Sandeep
On Wed, May 4, 2016 at 9:39 AM, Shubham Pathak
wrote:
> Hello Community,
>
> JdbcPOJOInputOperator reads from a database using JDBC API and emits a POJO
> for each record.
>
> In the current implementation, Date/Time/Timestamp fi
Hello Community,
JdbcPOJOInputOperator reads from a database using JDBC API and emits a POJO
for each record.
In the current implementation, Date/Time/Timestamp fields of the table are
mapped to "long" field in POJO. While this works fine, it is not intuitive.
I would like to enhance the operat
bright chen created APEXMALHAR-2076:
---
Summary: AbstractExactlyOnceKafkaOutputOperator didn't handle the
orderless of tuples in a window
Key: APEXMALHAR-2076
URL: https://issues.apache.org/jira/browse/APEXMALHAR-
[
https://issues.apache.org/jira/browse/APEXCORE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269856#comment-15269856
]
ASF GitHub Bot commented on APEXCORE-427:
-
Github user davidyan74 commented on t
Github user davidyan74 commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/323#issuecomment-216700890
@tweise please review
---
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 do
Github user davidyan74 closed the pull request at:
https://github.com/apache/incubator-apex-core/pull/308
---
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 th
[
https://issues.apache.org/jira/browse/APEXCORE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269822#comment-15269822
]
ASF GitHub Bot commented on APEXCORE-427:
-
GitHub user davidyan74 opened a pull
GitHub user davidyan74 opened a pull request:
https://github.com/apache/incubator-apex-core/pull/323
APEXCORE-427 disable tests that produce false negatives in travis
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davidyan74/inc
The problem with "SubGraph"/"SubDAG" and "CompositeOperator" names is
that they give priority to Graph/DAG or Operator behavior. Module is
something in between as it exposes both operator properties and DAG
properties and a name should reflect that or be neutral.
Thank you,
Vlad
On 5/3/16 1
[
https://issues.apache.org/jira/browse/APEXCORE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Yan resolved APEXCORE-330.
Resolution: Fixed
Fix Version/s: 3.4.0
> Ability to obtain a thread dump from a container
>
[
https://issues.apache.org/jira/browse/APEXCORE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269721#comment-15269721
]
ASF GitHub Bot commented on APEXCORE-330:
-
Github user asfgit closed the pull re
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-apex-core/pull/321
---
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
[
https://issues.apache.org/jira/browse/APEXCORE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269703#comment-15269703
]
ASF GitHub Bot commented on APEXCORE-442:
-
Github user asfgit closed the pull re
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-apex-core/pull/322
---
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
[
https://issues.apache.org/jira/browse/APEXCORE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269622#comment-15269622
]
ASF GitHub Bot commented on APEXCORE-442:
-
GitHub user davidyan74 opened a pull
GitHub user davidyan74 opened a pull request:
https://github.com/apache/incubator-apex-core/pull/322
APEXCORE-442 Removed incubator wording except mailing lists and repository
names
@tweise please review
You can merge this pull request into a Git repository by running:
$ git p
[
https://issues.apache.org/jira/browse/APEXCORE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269589#comment-15269589
]
ASF GitHub Bot commented on APEXCORE-442:
-
Github user tweise commented on the p
Github user tweise commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/317#issuecomment-216664545
The infra team has still not renamed the repositories. So please exclude
the github mirror references from this PR.
---
If your project is set up for it, y
[
https://issues.apache.org/jira/browse/APEXCORE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269532#comment-15269532
]
ASF GitHub Bot commented on APEXCORE-330:
-
Github user davidyan74 commented on a
Github user davidyan74 commented on a diff in the pull request:
https://github.com/apache/incubator-apex-core/pull/321#discussion_r61951218
--- Diff: engine/src/main/java/com/datatorrent/stram/cli/ApexCli.java ---
@@ -3366,6 +3370,28 @@ public void execute(String[] args, ConsoleRead
I agree with David that a Module is too abstract and within Apex doesn't
describe the concept it is used for.
If we have consensus to change this name then Ilya's suggestion of calling
it a "SubGraph" IMO is quite good.
It is a short name and relevant to the concept.
On Tue, May 3, 2016 at 11:
I vote we stay with Module -- there are bigger fish to fry.
The word means "modular unit" and is a valid candidate for use in any
context where that meaning fits.
The word Operator itself is overloaded in numerous contexts, both in
computing and in other fields.
The word Class is a common one fo
While you are right about "Evolving" state and having the ability to change
it, I think we should pause and consider backwards compatibility when
changing a major component like this one. I guess one factor that works in
your favor is that even though we do have code in our own Malhar repo using
th
[
https://issues.apache.org/jira/browse/APEXCORE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269210#comment-15269210
]
ASF GitHub Bot commented on APEXCORE-330:
-
Github user davidyan74 commented on a
Github user davidyan74 commented on a diff in the pull request:
https://github.com/apache/incubator-apex-core/pull/321#discussion_r61926171
--- Diff:
engine/src/main/java/com/datatorrent/stram/webapp/StramWebServices.java ---
@@ -122,7 +124,11 @@
public static final String P
[
https://issues.apache.org/jira/browse/APEXCORE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269200#comment-15269200
]
ASF GitHub Bot commented on APEXCORE-330:
-
Github user davidyan74 commented on a
Github user davidyan74 commented on a diff in the pull request:
https://github.com/apache/incubator-apex-core/pull/321#discussion_r61925721
--- Diff: engine/src/main/java/com/datatorrent/stram/StramUtils.java ---
@@ -81,4 +89,48 @@
}
}
+ public static JSON
[
https://issues.apache.org/jira/browse/APEXCORE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269198#comment-15269198
]
ASF GitHub Bot commented on APEXCORE-330:
-
Github user davidyan74 commented on a
Github user davidyan74 commented on a diff in the pull request:
https://github.com/apache/incubator-apex-core/pull/321#discussion_r61925623
--- Diff: engine/src/main/java/com/datatorrent/stram/StramUtils.java ---
@@ -81,4 +89,48 @@
}
}
+ public static JSON
[
https://issues.apache.org/jira/browse/APEXCORE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269195#comment-15269195
]
ASF GitHub Bot commented on APEXCORE-330:
-
Github user davidyan74 commented on a
Github user davidyan74 commented on a diff in the pull request:
https://github.com/apache/incubator-apex-core/pull/321#discussion_r61925340
--- Diff: engine/src/main/java/com/datatorrent/stram/cli/ApexCli.java ---
@@ -3366,6 +3370,28 @@ public void execute(String[] args, ConsoleRead
Why not rename Module to SubGraph? CompositeOperator is a rather unwieldy term
- there’s already some pretty hefty operator names in Malhar :)
On 5/3/16, 9:47 AM, "Amol Kekre" wrote:
>This is good time to make the change as the api is evolving and does not
>have a widespread adoption. I would
This is good time to make the change as the api is evolving and does not
have a widespread adoption. I would prefer to simply change it too.
Thks
Amol
On Tue, May 3, 2016 at 9:12 AM, David Yan wrote:
> Hi Pramod,
>
> The existing Module class is marked "InterfaceStability.Evolving" and
> there
Hi Pramod,
The existing Module class is marked "InterfaceStability.Evolving" and
therefore we don't guarantee backward compatibility. Also there are
probably very very few users, if any, who use any class derived from the
current Module because of the recent introduction of the concept.
I think a
+1 for CompositeOperator
On Mon, May 2, 2016 at 10:55 PM, Pramod Immaneni
wrote:
> I don't think we should rename Module to CompositeOperator as it will break
> backwards compatibility. If this is something we want to go forward with
> then we should think about depreacting Module.
>
> Thanks
>
[
https://issues.apache.org/jira/browse/APEXMALHAR-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandni Singh reassigned APEXMALHAR-2073:
-
Assignee: Chandni Singh
> Intermittent test case failure:
> ManagedStateImp
[
https://issues.apache.org/jira/browse/APEXCORE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268921#comment-15268921
]
ASF GitHub Bot commented on APEXCORE-107:
-
Github user tushargosavi commented on
Github user tushargosavi commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/313#issuecomment-216571779
changed the name of Vertex to GenericOperator
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
shubham pathak created APEXMALHAR-2075:
--
Summary: Support fields of type Date,Time and Timestamp in Pojo
Class for JdbcPOJOInputOperator
Key: APEXMALHAR-2075
URL: https://issues.apache.org/jira/browse/APEXMA
shubham pathak created APEXMALHAR-2074:
--
Summary: Support fields of type Date,Time and Timestamp in Pojo
Class for JdbcPOJOInputOperator
Key: APEXMALHAR-2074
URL: https://issues.apache.org/jira/browse/APEXMA
[
https://issues.apache.org/jira/browse/APEXMALHAR-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep Deshmukh updated APEXMALHAR-2073:
-
Summary: Intermittent test case failure:
ManagedStateImplTest.testFreeWindowT
Sandeep Deshmukh created APEXMALHAR-2073:
Summary: intermittent test case failure:
ManagedStateImplTest.testFreeWindowTransferRaceCondition:200 » NullPointer
Key: APEXMALHAR-2073
URL: https://issues.apache
44 matches
Mail list logo
