[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15747682#comment-15747682
 ] 

ASF GitHub Bot commented on APEXMALHAR-2368:
--------------------------------------------

GitHub user Hitesh-Scorpio opened a pull request:

    https://github.com/apache/apex-malhar/pull/523

    APEXMALHAR-2368 code changes to optimize memory usage in JdbcPoll ope…

    …rator @DT-Priyanka @tushargosavi @bhupeshchawda please review

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Hitesh-Scorpio/apex-malhar 
APEXMALHAR-2368_JDBCPollInput

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/apex-malhar/pull/523.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #523
    
----
commit b444bf587c58eaae5bb4f048c08c98335e025b62
Author: Hitesh-Scorpio <forhitesh...@gmail.com>
Date:   2016-12-13T14:09:43Z

    APEXMALHAR-2368 code changes to optimize memory usage in JdbcPoll operator

----


> JDBCPollInput operator reads extra records when 1.5M records are added to a 
> blank input table
> ---------------------------------------------------------------------------------------------
>
>                 Key: APEXMALHAR-2368
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2368
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>            Reporter: Hitesh Kapoor
>
> JDBCPollInput operator reads extra records when 1.5 million new records are 
> added to the input table.
> Operator information:
> Operator location: malhar-library
> Available since: 3.5.0
> Operator state: Evolving
> Operator: 
> com.datatorrent.lib.db.jdbc.AbstractJdbcPollInputOperator
> com.datatorrent.lib.db.jdbc.JdbcPOJOPollInputOperator
> Observed only when >=1.5 million records are inserted into the table.
> Not observed with 1million records



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to