https://linen.dev logo
Join Slack
Powered by
<@U04S8PLJWMT> I am getting this error destination...
# replication-ask-ai
r
@kapa.ai I am getting this error destination ERROR java.lang.IllegalArgumentException: No enum constant io.airbyte.integrations.destination.mssql.v2.convert.MssqlType.INT for MS SQL Server v2.2.12 destination connector. Isn't this resolved in 2.2.9 version. If so why Iam getting this error?
k
You’re hitting a known MSSQL destination v2 issue. From the GitHub issues: - The 
No enum constant <http://io.airbyte.integrations.destination.mssql.v2.convert.MssqlType.INT|io.airbyte.integrations.destination.mssql.v2.convert.MssqlType.INT>
error was originally reported on v2.2.6 and the reporter confirmed it was fixed for them when they upgraded to v2.2.9. [[MSSQL INT issue](https://github.com/airbytehq/airbyte/issues/59674)] - However, a newer issue shows the same error still occurring on later versions, including v2.2.7 and v2.2.13, and mentions similar problems for 
MssqlType.FLOAT
and 
MssqlType.NUMERIC
. This newer issue is still open. [[MSSQL INT open](https://github.com/airbytehq/airbyte/issues/61387)] So: - Yes, one instance of the bug was resolved for at least some cases by 2.2.9, but - The knowledge sources show that the problem (or a closely related one) still exists in later versions, and there is no confirmation in the sources that it is fully fixed for all schemas or data types. Because the open issue does not mention 2.2.12 specifically, I cannot say exactly why it still occurs in your case, only that the bug is not fully resolved according to the latest available information. [[MSSQL INT open](https://github.com/airbytehq/airbyte/issues/61387)] Given this, the best next step is to: 1. Compare your error and logs with the open issue 
#61387
and, if they match, add your version (2.2.12), schema details, and logs there so the maintainers can see it’s still reproducible. [[MSSQL INT open](https://github.com/airbytehq/airbyte/issues/61387)] 2. If possible, test with the latest released 
destination-mssql
version; the knowledge sources do not state whether a fix after 2.2.13 exists.
r
@kapa.ai Is this bug resolved in MS SQL Server v2.2.14 version?
k
A message from kapa.ai
Based on the available knowledge sources, it is not clear that this bug is resolved in 
destination-mssql
v2.2.14. What we know: - The original 
<http://MssqlType.INT|MssqlType.INT>
error was reported and a user confirmed it was fixed for them when upgrading to v2.2.9. [[MSSQL INT closed](https://github.com/airbytehq/airbyte/issues/59674)] - A newer, still-open issue shows the same error (and similar ones for 
FLOAT
and 
NUMERIC
) occurring on later versions, including 2.2.7 and 2.2.13. [[MSSQL INT open](https://github.com/airbytehq/airbyte/issues/61387)] - The MSSQL destination changelog entry for 2.2.14 only mentions “Upgrade to Bulk CDK 0.1.61” and does not explicitly state a fix for the 
MssqlType.*
enum errors. [[MSSQL changelog](https://docs.airbyte.com/integrations/destinations/mssql#changelog)] Because there is no explicit mention of this bug being fixed in 2.2.14 in the provided sources, I cannot confidently say it is resolved in that version. If you can, I’d recommend: 1. Testing your sync with 2.2.14. 2. If the error persists, commenting on the open GitHub issue 
#61387
with your connector version, schema, and logs so maintainers can confirm the status. [[MSSQL INT open](https://github.com/airbytehq/airbyte/issues/61387)]
7 Views
Open in Slack
PreviousNext
Powered by