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
print(f"Current entry (transaction id = {latest_entry['transactionId']}) in collection {latest_entry['collectionId']}: {latest_entry['contents']}")
194
202
```
195
203
196
-
The print function will return "Hello world!", as that is the message in the ledger that that corresponds to the transaction ID.
204
+
The print function will return "Hello world!", as that is the message in the ledger that that corresponds to the transaction ID and is the latest transaction.
197
205
198
206
## Full sample code
199
207
@@ -210,12 +218,11 @@ from azure.mgmt.confidentialledger.models import ConfidentialLedger
210
218
211
219
from azure.confidentialledger import ConfidentialLedgerClient
212
220
from azure.confidentialledger.certificate import ConfidentialLedgerCertificateClient
213
-
from azure.confidentialledger import TransactionState
print(f"Current entry (transaction id = {latest_entry['transactionId']}) in collection {latest_entry['collectionId']}: {latest_entry['contents']}")
293
300
```
294
301
302
+
## Pollers
303
+
304
+
If you would like to wait for your write transaction to be committed to your ledger you can use the `begin_create_ledger_entry` function. This will return a poller to wait until the entry is durably committed.
Querying an older ledger entry requires the ledger to read the entry from disk and validate it. You can use the `begin_get_ledger_entry` function to create a poller that will wait until the queried entry is in a ready state to view.
Other Azure confidential ledger articles can build upon this quickstart. If you plan to continue on to work with subsequent quickstarts and tutorials, you may wish to leave these resources in place.
0 commit comments