[GitHub] apex-malhar pull request #292: APEXMALHAR-1957: Updated HBase Input Operator

Github user chinmaykolhatkar commented on a diff in the pull request: https://github.com/apache/apex-malhar/pull/292#discussion_r66887202 --- Diff: contrib/src/main/java/com/datatorrent/contrib/hbase/HBasePOJOInputOperator.java --- @@ -37,20 +37,21 @@ import

[GitHub] apex-malhar pull request #292: APEXMALHAR-1957: Updated HBase Input Operator

Github user chinmaykolhatkar commented on a diff in the pull request: https://github.com/apache/apex-malhar/pull/292#discussion_r66886863 --- Diff: contrib/src/main/java/com/datatorrent/contrib/hbase/HBasePOJOInputOperator.java --- @@ -69,116 +70,105 @@ public Object

[jira] [Commented] (APEXMALHAR-1957) Improve HBasePOJOInputOperator with support for threaded read

[ https://issues.apache.org/jira/browse/APEXMALHAR-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328593#comment-15328593 ] ASF GitHub Bot commented on APEXMALHAR-1957: Github user chinmaykolhatkar commented on a

[GitHub] apex-malhar pull request #292: APEXMALHAR-1957: Updated HBase Input Operator

Github user chinmaykolhatkar commented on a diff in the pull request: https://github.com/apache/apex-malhar/pull/292#discussion_r66885832 --- Diff: contrib/src/main/java/com/datatorrent/contrib/hbase/HBaseScanOperator.java --- @@ -40,27 +51,107 @@ * @tags hbase, scan, input

[jira] [Commented] (APEXMALHAR-1957) Improve HBasePOJOInputOperator with support for threaded read

[ https://issues.apache.org/jira/browse/APEXMALHAR-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328590#comment-15328590 ] ASF GitHub Bot commented on APEXMALHAR-1957: Github user chinmaykolhatkar commented on a

[jira] [Commented] (APEXMALHAR-1957) Improve HBasePOJOInputOperator with support for threaded read

[ https://issues.apache.org/jira/browse/APEXMALHAR-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328481#comment-15328481 ] ASF GitHub Bot commented on APEXMALHAR-1957: Github user chinmaykolhatkar commented on a

[GitHub] apex-malhar pull request #292: APEXMALHAR-1957: Updated HBase Input Operator

Github user chinmaykolhatkar commented on a diff in the pull request: https://github.com/apache/apex-malhar/pull/292#discussion_r66886741 --- Diff: contrib/src/main/java/com/datatorrent/contrib/hbase/HBasePOJOInputOperator.java --- @@ -69,116 +70,105 @@ public Object

[jira] [Commented] (APEXMALHAR-1957) Improve HBasePOJOInputOperator with support for threaded read

[ https://issues.apache.org/jira/browse/APEXMALHAR-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328582#comment-15328582 ] ASF GitHub Bot commented on APEXMALHAR-1957: Github user chinmaykolhatkar commented on a

[GitHub] apex-malhar pull request #292: APEXMALHAR-1957: Updated HBase Input Operator

Github user chinmaykolhatkar commented on a diff in the pull request: https://github.com/apache/apex-malhar/pull/292#discussion_r66885954 --- Diff: contrib/src/main/java/com/datatorrent/contrib/hbase/HBaseScanOperator.java --- @@ -40,27 +51,107 @@ * @tags hbase, scan, input

[GitHub] apex-malhar pull request #292: APEXMALHAR-1957: Updated HBase Input Operator

Github user chinmaykolhatkar commented on a diff in the pull request: https://github.com/apache/apex-malhar/pull/292#discussion_r66884310 --- Diff: contrib/src/main/java/com/datatorrent/contrib/hbase/HBaseFieldValueGenerator.java --- @@ -0,0 +1,65 @@ +/** + * Licensed to

[GitHub] apex-malhar pull request #302: [APEXMALHAR-139] Make Sigma Operator Partitio...

Github user chinmaykolhatkar commented on a diff in the pull request: https://github.com/apache/apex-malhar/pull/302#discussion_r66880779 --- Diff: library/src/main/java/com/datatorrent/lib/math/AbstractOutput.java --- @@ -38,23 +38,23 @@ * Double type output. */

[jira] [Commented] (APEXMALHAR-139) Make sigma operator partition-able

[ https://issues.apache.org/jira/browse/APEXMALHAR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328436#comment-15328436 ] ASF GitHub Bot commented on APEXMALHAR-139: --- Github user chinmaykolhatkar commented on a

[GitHub] apex-malhar pull request #317: APEXMALHAR-2117 Generate default queryStmt ev...

GitHub user chinmaykolhatkar opened a pull request: https://github.com/apache/apex-malhar/pull/317 APEXMALHAR-2117 Generate default queryStmt even if its set to empty string Also added missing hsqldb mavne dependency for test scope. @sandeepdeshmukh Can you please review

[jira] [Created] (APEXMALHAR-2117) JDBCLoader for Enricher should generate default queryStmt even when value is empty string

Chinmay Kolhatkar created APEXMALHAR-2117: - Summary: JDBCLoader for Enricher should generate default queryStmt even when value is empty string Key: APEXMALHAR-2117 URL:

[jira] [Resolved] (APEXMALHAR-2111) Projection Operator config params shall use List instead of comma-separated field names

[ https://issues.apache.org/jira/browse/APEXMALHAR-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kolhatkar resolved APEXMALHAR-2111. --- Resolution: Done Fix Version/s: 3.5.0 > Projection Operator

[jira] [Commented] (APEXMALHAR-2111) Projection Operator config params shall use List instead of comma-separated field names

[ https://issues.apache.org/jira/browse/APEXMALHAR-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327897#comment-15327897 ] ASF GitHub Bot commented on APEXMALHAR-2111: Github user asfgit closed the pull request

[GitHub] apex-malhar pull request #311: APEXMALHAR-2111 Projection Operator config ch...

Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/311 --- 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

new method emitMessage() in Kafka Operator

Hi All, I am proposing to add new API in 0.8 version of AbstractKafkaInputOperator: void emitMessage(KafkaMessage message). "message" has details like offset, kafkapartition, value of the message. By adding this, users have more control over the message. Callback of this method would be in