Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Incremental mode does not work without error message

The JDBC CONSUMER is working to read hive table data with incrememtal mode.

The code is shown below.

SELECT datetime, timestemp, col1, col2, col3 FROM database.hivetable WHERE timestemp > ${OFFSET} ORDER BY timestemp initial offset : 0 offset column : timestemp

If Preview is executed, there is no error message but data is not moved (to Trash destination) There is no error message, so I can not find the cause.

The code below reads the data well.

SELECT datetime, timestemp, col1, col2, col3 FROM database.hivetable

The timestemp column is double type(also testing bigint type) of hive which converts datetime to unix epoch timestemp. I do not know why the timestemp column is not well working with respect to offset. I want to know if there are related issues, or if there is a reason to guess.

Incremental mode does not work without error message

The JDBC CONSUMER is working to for read hive table data with incrememtal mode.

The code is shown below.

SELECT datetime, timestemp, col1, col2, col3 FROM database.hivetable WHERE timestemp > ${OFFSET} ORDER BY timestemp initial offset : 0 offset column : timestemp

If Preview is executed, there is no error message but data is not moved (to Trash destination) There is no error message, so I can not find the cause.

The code below reads the data well.

SELECT datetime, timestemp, col1, col2, col3 FROM database.hivetable

The timestemp column is double type(also testing bigint type) of hive which converts datetime to unix epoch timestemp. I do not know why the timestemp column is not well working with respect to offset. I want to know if there are related issues, or if there is a reason to guess.

Incremental mode does not work without error message

The JDBC CONSUMER is working for read hive table data with incrememtal mode.

The code is shown below.

SELECT datetime, timestemp, col1, col2, col3 FROM database.hivetable WHERE timestemp > ${OFFSET} ORDER BY timestemp initial offset : 0 offset column : timestemp

If Preview is executed, there is no error message but data is not moved (to Trash destination) There is no error message, so I can not find the cause.

The code below reads the data well.

SELECT datetime, timestemp, col1, col2, col3 FROM database.hivetable

The timestemp column is double type(also testing bigint type) of hive which converts datetime to unix epoch timestemp. I do not know why the timestemp column is not well working with respect to offset. I want to know if there are related issues, or if there is a reason to guess.