go to post Tani Frankel · Aug 27 I'd look at JSONata. I played with it a while ago... And if you want to utilize our Python support, take a look at the Python edition of it: jsonata-python.
go to post Tani Frankel · Aug 14 In general (and messages and streams are just one example) there is a trade-off between more traceability and visibility vs. storage/space (and performance). QuickStream is indeed a mechanism used internally to address the performance and storage concerns, but, to complete this with a traceability option, there is also a dedicated Business Operation that can add the desired data - see Enhanced Debugging and the introduction of HS.Util.Trace.Operations. This simply adds more calls in the session, to this Operation which (could) include the stream data. The advantage of this is that you can turn it on or off, and you can control also the "level" of tracing. Take into account of course that this needs to be done ahead of what you want to trace/visualize, you can't "apply" this retroactively.
go to post Tani Frankel · Aug 7 By the way (apart from the /api/atelier/.../query API which I mentioned in my other response, which is a built-in API) there is also this custom API which @Evgeny Shvarov built - sql-rest-api, see also related article.
go to post Tani Frankel · Aug 7 This should work. What HTTP Method are you using POST (or GET)? What HTTP status are you getting - 200 OK (or 405 Method Not Allowed)?
go to post Tani Frankel · Aug 6 See using the Query API of the "Source Code File REST API" - Tutorial -> Performing an SQL Query Reference -> Query
go to post Tani Frankel · Jul 25 If you use the InterSystems CLI vis your OS shell, you can also simply run: #iris python instancename See the iris command docs (at least for some OSs).
go to post Tani Frankel · Jul 20 Examining the Audit database (specifically the LoginFailure event, and perhaps Protect; make sure they are Enabled for your testing) might also be helpful.
go to post Tani Frankel · Jul 16 Hi Dmitrii, From the discussion in the comments it seems like you're trying to use "Workers", but did you try to use the Event mechanism for your use-case? See also this related article (and this one as well). By the way here's a Docs reference of using this from Python. I don't have a wider context of this, but in the IRIS Interoperability functionality, behind the scenes of the Interoperability components, and the Messages and Queues managed there, this Event mechanism is used. So perhaps if you are already using IRIS's Interoperability capabilities, you can implement this in the higher level of the Business Components in your Interoperability Production, rather than with the lower level code using the Event class. The Workers mechanism you tried to use is intended more for distributing parallel work, and the Event API is more for messaging and queuing scenarios, which sounds more like your use-case. This article might also be of interest to you as it discusses moving from "Workers" to "Events".
go to post Tani Frankel · Jun 22 See related post: SMART on FHIR app - Sample with Hands-on Exercise/Workshop Instructions
go to post Tani Frankel · Jun 22 See related post: SMART on FHIR app - Sample with Hands-on Exercise/Workshop Instructions
go to post Tani Frankel · Jun 22 See related post: SMART on FHIR app - Sample with Hands-on Exercise/Workshop Instructions
go to post Tani Frankel · Jun 22 See related post: SMART on FHIR app - Sample with Hands-on Exercise/Workshop Instructions
go to post Tani Frankel · Jun 22 See related post: SMART on FHIR app - Sample with Hands-on Exercise/Workshop Instructions
go to post Tani Frankel · Jun 22 The related short videos have been uploaded and published, so updated the post accordingly.
go to post Tani Frankel · Mar 2 See Cloud Storage APIs and Cloud Storage Adapters. See also this example by @Keren Skubach (it uses Azure and not AWS, but the principal is the same).
