Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

The results vary depending which tool you actually use to execute the query.

Salesforce workbench => scientific notation Salesforce developer console => decimal value

Streamsets preview => decimal value Streamsets pipeline/logfile/source offset => scientific notation

But in any case executing the soql with scientific notation leads to an error, whether you use streamsets, developer console or workbench. => Streamsets, workbench

This is the part I changed in ForceSource.java to reconvert the offset into a decimal, it's more like a hack than a fix I guess, respecting the actual datatype of the offset column would make more sense or storing the offset in the correct format may be a better approach than reconvert in the prepare query part.

Best regards Peter

The results vary depending which tool you actually use to execute the query.

Salesforce workbench => </del><ins><a href=Salesforce workbench => scientific notation" src="https://drive.google.com/open?id=1XaPHsyDbbpfdk1xSfvLae2ZaKTCiVj1D"> Salesforce developer console => decimal valuenotation

Streamsets preview => </del><ins><a href=Salesforce developer console => decimal value" src="https://drive.google.com/open?id=1jcd3H41DnGfVU9_DOX_L6ho7Qno656TN"> Streamsets pipeline/logfile/source offset => </del><ins>value</a></p> <p><a href=Streamsets preview => decimal value

Streamsets pipeline/logfile/source offset => scientific notation" src="https://drive.google.com/open?id=1ncWNzwSVUk5b12Ki8w0IvSh5qK8PUocB">notation

But in any case executing the soql with scientific notation leads to an error, whether you use streamsets, developer console or workbench. => StreamsetsStreamsets, workbenchworkbench

ThisThis is the part I changed in ForceSource.java to reconvert the offset into a decimal, it's more like a hack than a fix I guess, respecting the actual datatype of the offset column would make more sense or storing the offset in the correct format may be a better approach than reconvert in the prepare query part.

Best regards Peter

The results vary depending which tool you actually use to execute the query.

Salesforce workbench => scientific notation

Salesforce developer console => decimal value

Streamsets preview => decimal value

Streamsets pipeline/logfile/source offset => scientific notation

But in any case executing the soql with scientific notation leads to an error, whether you use streamsets, developer console or workbench. => Streamsets, workbench

This is the part I changed in ForceSource.java to reconvert the offset into a decimal, it's more like a hack than a fix I guess, respecting the actual datatype of the offset column would make more sense or storing the offset in the correct format may be a better approach than reconvert in the prepare query part.

If this will/can not be compensated on Streamsets side and we have to wait until Salesforce changes this (very unlikely, only 40 votes of 400 to address this issue) it should be clearly pointed out in the Saleforce_lib connector documentation that numbers longer than 8 digits are not functional as offset.

Best regards Peter