The reason we need Java 21 support is we have several components that are based on EnsLib.PEX.BusinessService and written in Java 11. We need to migrate this code to Java 21. Perhaps we will be okay if we don't leverage any Java 21 specific capability, but still wanted to get some reassurance.
Which we already know. We're planning for next years upgrade hence we need a definitive answer of yes or no for any 2024 version.
We're currently on version 2023.1.3 and plan to upgrade to a version of 2024 sometime in 2025. Still the links below don't give a definitive answer for either release.
Is there a benefit to compiling mapped classes first before all others?
Tried using this repo in GitHub Codespaces and even locally at the docker-compose command is not correct and does not create the container.
I split up the commands to just do docker-compose build and then docker-compose up -d and that worked.
I suspect the syntax on docker-compose --progress plain build is wrong.
One more question: How did you configure the Pages section of the repo? I'm getting a 404 error when i try to access the page.
This works fine as long as the everything is in the same repo, but ideally you would want to have a separate repo for the documentation. There will be other documentation besides the class files and we want to keep them on a distinct cadence from code updates.
When I try to use the INPUT reference to another repo, it fails with source is not a readable file or directory... skipping. I've read through the documentation and I can't find anything related to referencing a remote repo.
I'll post to their listserv and see if this is possible.
This looked interesting so I tried it on one of my repo's and it seems to create the documentation, but when I open the index.html page I don't see the navigation display for the classes; it just displays the header page. I did notice at the end the following:
Running plantuml with JAVA...
type lookup cache used 0/65536 hits=0 misses=0
symbol lookup cache used 0/65536 hits=0 misses=0
Perhaps this is an issue?
What is the earliest version of IRIS that can connect to AWS S3 buckets?
Mark;
Thanks; this is helpful and I will forward to our Observability team.
That is my plan to attend the IKO session today and Friday. Hoping for some enlightenment on the topic.
Unfortunately this doesn't really address my question. I'm looking for real world use of IKO.
Yes we have faced this issue with CacheStream global growing out of control. We have had to create custom purge utilities to clean this data up as well as making sure any of our persistent classes that leverage a Stream class will trigger deletes on the stream when our record is deleted.
You would think the product would be able to handle this as part of cleanup of Ens.messageHeader, but alas that is not the case.
Looking for both.
Is the container distribution site down as well?
Anton, is there a minimum configuration to run this on a MacBook? The IRIS instance never starts - it's always in Pending status and the longhorn-system shows Init:0/1.
I will move on and try it in Azure, but was hoping to see how it looks on my local.
Thank you Vitaliy!
Well you can have more than one cursor. The main problem is in the second query, we joined Ens.Messageheader to EnsLib_HL7.Message and referencing the Identifier field of EnsLib_HL7.Message was causing a compiler error on the SQL query. Once that field was removed, everything is fine. The oddity is the query would work fine on the Management Portal SQL web page, but would not work in code.
The error was multiple Referenced macro not defined errors.
Is the video of this webinar available for viewing?
Found the documentation to set this up.
Adapting the sample code to connect to my own local IRIS, how do I define the location for intersystems-iris-native. I see this line of code const irisnative = require('intersystems-iris-native'). Do I need to make a copy of one of the iris.node files from the bin directory and add it it node-modules?
Also I am using node v13.8.0 - will iris1000.node work is do I need one specific to that version?
The fix for this is to delete ~/.docker/config.json (https://superuser.com/questions/1401705/docker-gcloud-how-to-fix-docker-credential-gcloud-not-installed-or-not-avail)
This fixed the issue and I am able to run docker images again.
When I run the docker up command from VSCode or if I try to run this from the command line I am getting the following error: docker.credentials.errors.InitializationError: docker-credential-gcloud not installed or not available in PATH
David
Is the current R4 support built into the FHIR Repository or is this represented somewhere else? Do you have any documentation?
Is there any plan to get rid of the intermediate data model and support FHIR data model directly, or is SDA3 still your approach to supporting it?
Also, do you have a time table for when STU4 support will be available in 2020.1?
David
Evgeny;
This did work so thanks for the tip!
David
When I try this on my laptop I am getting the following error: The terminal process terminated with exit code: 1
Looking at the terminal output everything seems normal up to that point. Have you encountered this issue before?
David
Eduard, that's a good suggestion, but one issue I see is that if you are processing millions of documents, that's a lot of database overhead. Using a simple global reference with locks would work better as you would only have n files persisted up to the Pool Size.
My next challenge is to determine a better way for the file service to pick off files from the OS folder without loading all the files into a potentially massive result set which can blow out local memory and in extreme cases quickly blow out CacheTemp DB size.
Okay, that setting eventually worked. I guess the services takes many minutes when there is large number of documents sitting in the OS folder.
One more question - is there a way to use negation on the file spec - e.g. create another service that looks for documents that don't match the specific pattern? I don't see anything obvious reading the code which means I would need to create a custom service to do this.
I would like to have multiple services handling the same OS folder.
I could use Pool Size > 1 but then there is conflict between the jobs when they try to access the same file.
Out of the box there is no way to reference the %Source value of the recordmap via the UI. You will need to create a custom class as shown in previous replies/answers on this thread.
It is interesting though that if I modify the .int file directly with pContext.Document.%Source and compile, the code compiles AND the rule works.
So this must be a defect in IS code.
Also, it is disappointing that the documentation around RecordMapper usage is so poor that you need to go on this long debug sessions to figure out how things really work.