-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Read Data after enabling TTL on container level #457
Comments
I am facing same issue. Look like cosmos OLTP connector not working with TTL . I have faced it when TTL on (No default) and on with some seconds set in edit filed . |
Hi, can you tell us which version of the Spark Connector you are using? Also it would be great to see the error details (error message with callstack) of the failure. Thanks, |
@FabianMeiswinkel , Stack trace Driver stacktrace: |
Hi, I am using: Databricks Runtime Version: 8.3 (Apache Spark 3.1.1, Scala 2.12) and/or 8.4 (Apache Spark 3.1.2, Scala 2.12) Stacktrace attached. Thanks, |
@FabianMeiswinkel Regards, |
Hi Team,
I am trying to read data from a Cosmos(SQL API) container using the custom query option, resulting in errors.
Setup of the container - Enable TTL with a default value of 1 week(72460*60)
What works -
What does not work-
But, if I remove the TTL setting on the container I am able read data using azure-cosmos DB-spark connector
Is this expected behavior with TTL turned on?
The text was updated successfully, but these errors were encountered: