You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/SetupGuide_Java.md
+7
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,7 @@
19
19
-[Array](#array)
20
20
-[Single Row](#single-row)
21
21
-[Trigger Binding](#trigger-binding)
22
+
-[Known Issues](#known-issues)
22
23
23
24
## Setup Function App
24
25
@@ -421,3 +422,9 @@ Note: This tutorial requires that a SQL database is setup as shown in [Create a
421
422
## Trigger Binding
422
423
423
424
> Trigger binding support is only available for in-proc C# functions at present.
425
+
426
+
## Known Issues
427
+
The [Azure Functions Java worker](https://github.com/Azure/azure-functions-java-worker) uses the [GSON library](https://github.com/google/gson) to serialize and deserialize data. Since we are unable to customize the GSON serializer in the Java worker, there are limitations with the default GSON serializer settings.
428
+
- GSON is unable to parse `DATE` and `TIME` values from the SQL table as `java.sql.Date` and `java.sql.Time` types. The current workaround is to use String. Tracking issue: https://github.com/Azure/azure-functions-sql-extension/issues/422.
429
+
- On Linux, `java.sql.Timestamp` type gets serialized with an extra comma, causing the upsertion to fail. The current workaround is to use String. Tracking issue: https://github.com/Azure/azure-functions-sql-extension/issues/521.
0 commit comments