-
Notifications
You must be signed in to change notification settings - Fork 233
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
TwinCollection Max Depth Issue #699
Comments
Since the max depth appears to have changed from 5 to 10 from the service's perspective, it's probably a good idea for the SDK to just not care about the twin depth. We should definitely remove the code that validates that twin fits a certain depth |
Hi, is there an expected timeline for a new release which will include this fix? |
I'm trying to get a new version of the SDK released with this fix by the end of this week. I'll update this thread once it is released |
As of this release, all SDK twin depth validation is removed, so I'm closing this issue |
@bouff, @morphvale, thank you for your contribution to our open-sourced project! Please help us improve by filling out this 2-minute customer satisfaction survey |
macOS 10.15.2
JDK 1.8
iot-service-client version 1.19.0
Description of the issue:
As per the IoT Hub documentation, the depth limitation for desired properties, reported properties, and tag is 10.
https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-device-twins#tags-and-properties-format
The value is currently hard-coded at 6.
https://github.com/Azure/azure-iot-sdk-java/blob/master/deps/src/main/java/com/microsoft/azure/sdk/iot/deps/twin/TwinCollection.java
This is essentially a reincarnation of the following issue:
#338
Would it be possible to either update the value (or remove that validation, as discussed in the previous issue)?
Code sample exhibiting the issue:
Console log of the issue:
Need Support?
The text was updated successfully, but these errors were encountered: