There are two ways to do that:
1. Mappings. Map classes and globals into the namespace you're querying from. This would work if there's no global/class collisions of course.
2. Custom queries. Here's an article on the topic. And here's an example.
3. Just set $namespace before running your query. Works only if you need to query one other namespace at a time. Example.
How did you remove the cycle?
Sure, just mount C:\InterSystems\IRISHealth\mgr\samples\ folder as a docker volume.
After that add a new Database from inside the container pointing to the mounted folder.
Article idea: InterSystems IRIS CUDA image
There's a way to use GPUs/CUDA from inside the container. Describe how to build an InterSystems IRIS image with CUDA support.
All arguments are passed automatically:
.png)
And the routine:
.png)
Results in:
.png)
Well, in that case:
ClassMethod ToNato(t) [ CodeMode = call ]
{
^S
}And write everything in the S routine.
Article idea: Building IRIS images with Docker Build Mounts
From the docs on Docker Build Mounts:
RUN --mountallows you to create mounts that process running as part of the build can access. This can be used to bind files from other part of the build without copying, accessing build secrets or ssh-agent sockets, or creating cache locations to speed up your build.
This is a recent Docker feature allowing users to build compact images (since we no longer need to COPY everything inside). Try it out and write an article about it?
Check this example for required JARs. Specifically this line.
Sure, use INSERT with SELECT query. Where SELECT query is against your SQL gateway (via linked tables probably).
Have you tried to declare C# property like this:
.png)
public Dictionary<string, string> VarsXctsTU { get; set; }Please consider adding samples illustrating your issue:
Check this series of articles.
Great idea, Jeffrey!
I didn't know about this query. Awesome!
You're missing a JAR with net.sf.cglib.proxy.MethodInterceptor class.
if I type full command then it is working fine.
What full command?
I'm authorized in containers.intersystems.com in docker. Is that not enough? Interesting.
What happened to intersystems/arbiter? I can't find it in containers.intersystems.com registry:
>docker-ls.exe repositories --registry https://containers.intersystems.com
requesting list . done
repositories:
- intersystems/iris-community
- intersystems/iris-community-arm64
- intersystems/iris-ml-community
- intersystems/irishealth-aa-community
- intersystems/irishealth-community
- intersystems/irishealth-community-arm64
- intersystems/irishealth-ml-community
- intersystems/samHowever, a direct pull succeeds:
docker pull containers.intersystems.com/intersystems/arbiter:2021.1.0.215.0
2021.1.0.215.0: Pulling from intersystems/arbiter
f22ccc0b8772: Already exists
3cf8fb62ba5f: Already exists
e80c964ece6a: Already exists
cc40d98799c0: Pull complete
4179ff34652c: Pull complete
70ed38c703cc: Pull complete
ab1c2108b984: Pull complete
758289e88757: Pull complete
Digest: sha256:51c31749251bea1ab8019a669873fd33efa6020898dd4b1749a247c264448592
Status: Downloaded newer image for containers.intersystems.com/intersystems/arbiter:2021.1.0.215.0
containers.intersystems.com/intersystems/arbiter:2021.1.0.215.0What's msg?
Does Archive folder exist?
Enable CORS in your REST API.
The value has reached 7gb and now it has become a problem.
So, how's the memory consumption now?
Is there a way to do the same but for the query text and documents, and not document and documents?
regarding your comment around moving JSON parsing to BS, is there a reason for doing so?
In general it might be preferable to move from less structured data (JSON) to more structured data (Objects) as fast and as early in your processing pipeline as possible.
The reasons for it are varied but include:
So in your case I would have structured it like this:
It's also advantageous to move all parsing logic is in one place (Business Service) as it minimizes the amount of code written and frees Business Processes from the more low-level technical tasks which usually obfuscate the more high-level intent of a Business Process.