+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 11:20 AM, Pradeep A. Dalv
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()
>
> --prad
>
> On We
+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 = conn.getMetaData();
>
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()) {
System.out.println(rsColum
Hi All,
This issue occurs when we try to insert records in a table which has a lot
of data.
The setup method of JdbcPOJOInsertOutputOperator generates the metadata of
the columns in the table. To do so it fires a query of the form "Select *
from tablename" and the extracts the required meta data l
Hitesh Kapoor created APEXMALHAR-2290:
-
Summary: JDBC operator does not deploy after failure in certain
cases
Key: APEXMALHAR-2290
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2290
Projec