[ https://issues.apache.org/jira/browse/APEXMALHAR-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15591292#comment-15591292 ]
ASF GitHub Bot commented on APEXMALHAR-2290: -------------------------------------------- GitHub user Hitesh-Scorpio reopened a pull request: https://github.com/apache/apex-malhar/pull/452 APEXMALHAR-2290 Optimization to fetch meta data in JdbcPOJOInsertOutput Operator. @bhupeshchawda @chinmaykolhatkar please review You can merge this pull request into a Git repository by running: $ git pull https://github.com/Hitesh-Scorpio/apex-malhar APEXMALHAR-2290_JDBCMaxRows Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-malhar/pull/452.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 #452 ---- commit cff582f5581bd07e5ca3398a63b171fccd069785 Author: Hitesh-Scorpio <forhitesh...@gmail.com> Date: 2016-10-12T15:00:22Z APEXMALHAR-2290 fix to optimize the function which was populating meta data for columns ---- > JDBC operator does not deploy in certain cases > ---------------------------------------------- > > Key: APEXMALHAR-2290 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2290 > Project: Apache Apex Malhar > Issue Type: Bug > Reporter: Hitesh Kapoor > Assignee: Hitesh Kapoor > Fix For: 3.6.0 > > > In some cases the JDBC output operator does not deploy properly. The operator > gets killed and does not gets deployed. > The setup method uses "select * from tablename" to just get types of fields > in the table. If the tables already has lot of data then select queries runs > for more than 30 sec and the operator is killed -- This message was sent by Atlassian JIRA (v6.3.4#6332)