[jira] [Commented] (APEXCORE-560) Logical plan is not changed when all physical partitions of operator are removed from DAG

[ https://issues.apache.org/jira/browse/APEXCORE-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607577#comment-15607577 ] Tushar Gosavi commented on APEXCORE-560: I think activate/deactivate will be of

[jira] [Commented] (APEXMALHAR-2274) AbstractFileInputOperator gets killed when there are a large number of files.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607573#comment-15607573 ] Tushar Gosavi commented on APEXMALHAR-2274: --- you can take a look at FileSpl

[jira] [Updated] (APEXMALHAR-2314) Improper functioning in partitioning of sequentialFileRead property of FSRecordReader

[ https://issues.apache.org/jira/browse/APEXMALHAR-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Narkhede updated APEXMALHAR-2314: Description: Fix the StreamCodec for FSRecordReader, initially it was hashcode

[jira] [Commented] (APEXMALHAR-2315) Ignore Join Test for because of issues in POJOInnerJoinOperator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607564#comment-15607564 ] ASF GitHub Bot commented on APEXMALHAR-2315: Github user asfgit closed th

[GitHub] apex-malhar pull request #469: APEXMALHAR-2315 Ignore tests in sql which use...

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

[jira] [Created] (APEXMALHAR-2315) Ignore Join Test for because of issues in POJOInnerJoinOperator

Chinmay Kolhatkar created APEXMALHAR-2315: - Summary: Ignore Join Test for because of issues in POJOInnerJoinOperator Key: APEXMALHAR-2315 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2315

Re: data pull from JDBC

Hi Vinod, For Pojo, you need to define a class having all of your fields (which will be populated by data retrieved from jdbc table). In this class you also need to define getter/setter for each field. When you use JdbcPOJOInputOperator, provide the fully classified class name as input to this ope

Re: data pull from JDBC

Hi Vinod, Please have a look at the JdbcPOJOInputOperator which emits POJO records on the output port. ~ Bhupesh On Wed, Oct 26, 2016 at 6:51 AM, vinod sugur wrote:

data pull from JDBC

Hi, I am new to Apache Apex. I have developed a code by looking at JDBCInputOperator to move data from relational database to Hadoop. There is no transformation on data, it is just extract and load use case. I need to implement this approach to all tables that are part of relational schema. Ques

[jira] [Commented] (APEXMALHAR-2274) AbstractFileInputOperator gets killed when there are a large number of files.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606612#comment-15606612 ] Matt Zhang commented on APEXMALHAR-2274: - FileSystem.listStatusIterator() no

[jira] [Assigned] (APEXMALHAR-2233) Consolidate example apps into malhar apps

[ https://issues.apache.org/jira/browse/APEXMALHAR-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Velineni Lakshmi Prasanna reassigned APEXMALHAR-2233: - Assignee: Velineni Lakshmi Prasanna > Consolidate ex

Re: example applications in malhar

That would be great. There are a few things to consider when working on it: * preserve attribtion * ensure there is a test that runs the application in the CI * check that dependencies are compatible license * maybe extract common boilerplate code from pom.xml etc. Existing examples are under ht

Re: example applications in malhar

Can i work on this? Thanks Lakshmi Prasanna On Mon, Sep 12, 2016 at 9:41 PM, Ashwin Chandra Putta < ashwinchand...@gmail.com> wrote: > Here is the JIRA: https://issues.apache.org/jira/browse/APEXMALHAR-2233 > > On Tue, Sep 6, 2016 at 10:20 PM, Amol Kekre wrote: > > > Good idea to consolidate

[jira] [Resolved] (APEXMALHAR-2254) File input operator is not idempotent with closing files on replay

[ https://issues.apache.org/jira/browse/APEXMALHAR-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXMALHAR-2254. - Resolution: Fixed > File input operator is not idempotent with closing files

[jira] [Resolved] (APEXMALHAR-2270) AbstractFileInputOperator: During replay, inputStream should skip tuples

[ https://issues.apache.org/jira/browse/APEXMALHAR-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXMALHAR-2270. - Resolution: Fixed > AbstractFileInputOperator: During replay, inputStream sho

[jira] [Resolved] (APEXMALHAR-2269) AbstractFileInputOperator: During replay, IO errors not handled

[ https://issues.apache.org/jira/browse/APEXMALHAR-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni resolved APEXMALHAR-2269. - Resolution: REMIND For idempotency the failureHandling() method that processe

[GitHub] apex-malhar pull request #447: APEXMALHAR-2224 Fixed GenericFileOutputOperat...

GitHub user prasannapramod reopened a pull request: https://github.com/apache/apex-malhar/pull/447 APEXMALHAR-2224 Fixed GenericFileOutputOperator rotateCall. @yogidevendra please review You can merge this pull request into a Git repository by running: $ git pull https://github

[GitHub] apex-malhar pull request #448: APEXMALHAR-2254-2269-2270 Fix bugs on replay ...

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

[jira] [Commented] (APEXMALHAR-2224) GenericFileOutputOperator rotateCall fails if no data is written to the file

[ https://issues.apache.org/jira/browse/APEXMALHAR-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605738#comment-15605738 ] ASF GitHub Bot commented on APEXMALHAR-2224: GitHub user prasannapramod r

[GitHub] apex-malhar pull request #447: APEXMALHAR-2224 Fixed GenericFileOutputOperat...

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

[jira] [Commented] (APEXMALHAR-2224) GenericFileOutputOperator rotateCall fails if no data is written to the file

[ https://issues.apache.org/jira/browse/APEXMALHAR-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605737#comment-15605737 ] ASF GitHub Bot commented on APEXMALHAR-2224: Github user prasannapramod c

[jira] [Commented] (APEXMALHAR-2254) File input operator is not idempotent with closing files on replay

[ https://issues.apache.org/jira/browse/APEXMALHAR-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605695#comment-15605695 ] ASF GitHub Bot commented on APEXMALHAR-2254: Github user asfgit closed th

[jira] [Closed] (APEXCORE-564) We should be able to remove loggers level settings

[ https://issues.apache.org/jira/browse/APEXCORE-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale closed APEXCORE-564. Resolution: Won't Fix > We should be able to remove loggers level settings > -

[jira] [Commented] (APEXCORE-564) We should be able to remove loggers level settings

[ https://issues.apache.org/jira/browse/APEXCORE-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605201#comment-15605201 ] Priyanka Gugale commented on APEXCORE-564: -- okay closing the issue in that case