Fix sdkTimeFormat #335
Fix sdkTimeFormat #335
Conversation
OCI server accept millisecond not nanosecond
|
@mattn thanks for filing this, however the changes you've made would change the entire SDK to not have nanosecond precision. I think rather than changing the SDK, the service Logging Ingestion's PutLogs operation should accept nanosecond precision. I will follow up with the service team on that |
|
Yes, this is POC to let you known this issue. Feel free to close this after fixing your service. Thanks. |
|
Well, do you have plan to fix this issue in a few days/weeks or months? |
|
Hi @mattn - we are reviewing the issue and will get back with an estimate |
|
@mattn We have reviewed and will try to have deployed by end of month. |
|
Quick update, we are working on this change but its not ready for release yet. Will send out an update once we have clear dates for release. |
|
The fix has been made and tested. It is being deployed to production regions this week. Thank you for your patience. |
|
Thank you. Closing. |
|
Ah, sorry. Yet not deployed on my region. I'll close this if confirmed on my region. |
|
Deployment to OC1 Realm is completed now. |
|
@mattn this should be all set for you now to use. Can you try again and let us know if the problem is resolved? |
|
I confirmed OCI works without my changes. Thank you. |
3 participants
OCI server accept milliseconds not nanoseconds for any datetime formats. I noticed this issue because oracle/oci-dotnet-sdk does not get errors for loggingingestion.PutLogs but Go get errors. Python SDK might have same issue.
Related issue:
oracle/oci-python-sdk#333