Re: (APEXMALHAR-2290) JDBC operator does not deploy after failure in certain cases

2016-10-13 Thread Chinmay Kolhatkar
+1 On Thu, Oct 13, 2016 at 7:48 PM, Hitesh Kapoor wrote: > Hi All, > > Thank you for your suggestions. > Following the approach as suggested by Chinmay in option 1. > Will make the necessary code changes, test it and create a PR. > > --Hitesh > > On Thu, Oct 13, 2016 at

Re: (APEXMALHAR-2290) JDBC operator does not deploy after failure in certain cases

2016-10-13 Thread Hitesh Kapoor
Hi All, Thank you for your suggestions. Following the approach as suggested by Chinmay in option 1. Will make the necessary code changes, test it and create a PR. --Hitesh On Thu, Oct 13, 2016 at 11:20 AM, Pradeep A. Dalvi wrote: > +1 for Option 1 to use conn.getMetaData() >

Re: (APEXMALHAR-2290) JDBC operator does not deploy after failure in certain cases

2016-10-12 Thread Pradeep A. Dalvi
+1 for Option 1 to use conn.getMetaData() --prad On Wed, Oct 12, 2016 at 11:39 PM, Chinmay Kolhatkar wrote: > Hi Hitesh, > > Instead of limiting the row count please use one of the following 2 > approaches: > > 1. ResultSet rsColumns = null; > DatabaseMetaData meta =

Re: (APEXMALHAR-2290) JDBC operator does not deploy after failure in certain cases

2016-10-12 Thread Chinmay Kolhatkar
Hi Hitesh, Instead of limiting the row count please use one of the following 2 approaches: 1. ResultSet rsColumns = null; DatabaseMetaData meta = conn.getMetaData(); rsColumns = meta.getColumns(null, null, "tablename", null); while (rsColumns.next()) {