All
Accepted answers
Bob Kuszewski · Mar 3, 2020 go to post

Hi Adam - 

At the moment, the jar files are only distributed as part of IRIS (the Windows installer, Docker container, etc). If distributing the client libraries in a different manner would significantly improve your development cycle, please let me know.

-Bob

Bob Kuszewski · Mar 6, 2020 go to post

You're right, decimals aren't working properly with IRISList.  We have a fix for this in-process and expect to have it in our mid-year release.

Bob Kuszewski · Apr 11, 2020 go to post

Unfortunately, there is no IRIS client for Entity Framework on .NET Core available.  Could your application use ADO.NET or ODBC or IRISClient directly?

Bob Kuszewski · Apr 13, 2020 go to post

We have explored the idea of creating an official IRIS driver for EF Core, but are not currently working on one.  I think David (below) has a good idea for folks who are interested in making this happen.

Bob Kuszewski · Jun 12, 2020 go to post

Great minds think alike - one of my demos will be of using Kafka.  And I'd be thrilled to see yours on open exchange.

Bob Kuszewski · Oct 7, 2020 go to post

Good idea.  We're working on better processes for client distribution overall.

Bob Kuszewski · Jan 26, 2021 go to post

There is no pre-build IMAP adapter in Cache that I know of.  Maybe use the Java Gateway?

Bob Kuszewski · Mar 1, 2021 go to post

Hi Stefan - 
I'll try to answer your questions in order.  If you want to know more, let me know.

  • IKO does not currently configure any kubernetes ingress, but there is a service that is configured which you could choose to configure for external access (a load balancer, for example).  You can set this via spec.serviceTemplate.spec section of your iriscluster yaml.  That's a spec which gives details about the service that we create.  I like to use ClusterIP for the service type and then create an ingress to give me good control over what is exposed to the internet.  A bit more info can be found here:  https://kubernetes.io/docs/concepts/services-networking/service/#publis…
  •  
  • Regarding routing to individual hosts... From within the cluster (say another pod in the namespace) each other pod is accessible via it's hostname (for example, myCluster-data-0-1) and you can use the kubectl port forwarding feature to allow you administrative access as you may need.  For non-administrative workflows, I suggest creating kubernetes services that point to the subset(s) of pods you want to use for each type of production traffic you want to manage.
  •  
  • We are currently working on adding native support for IAM and SAM in IKO, which greatly simplifies installing these products in Kubernetes.  In the meantime, most use cases would want to run IAM inside the cluster by creating a series of kubernetes deployments, services, and ingress to deploy IAM.  I might be able to gin up an example if you're going this way.
     
Bob Kuszewski · Oct 27, 2021 go to post

We've tried to package up our best practices for deploying IRSI in K8s into the InterSystems Kubernetes Operator.  In other words, instead of documenting everything, we built a tool that automates what can be automated.
That said, it doesn't cover everything.  Your example question is a good one - should IRIS clusters be deployed into the same kubernetes cluster as your other workloads?  The right answer to that depends on your exact needs.
In general, you shouldn't deploy IRIS into a different Kubernetes cluster than the rest of your kubernetes-managed application.  However, I'd consider doing it if there were strong architectural/compliance reasons to keep the IRIS cluster separated from other applications.  

Feel free to reach out if you want someone to go over your situation give more proscriptive advice.

Bob Kuszewski · Nov 4, 2021 go to post

Embedded Python is a new feature being added in the upcoming IRIS 2021.2 and IRIS for Health 2021.2.  We're getting close to releasing a preview, but it's not yet available.  

Bob Kuszewski · Dec 20, 2021 go to post

Couchbase has JDBC and ODBC drivers.  Can your application design use the IRIS SQL Gateway?

Bob Kuszewski · Feb 16, 2022 go to post

I think we need a bit more info about your data structure and your environment. 

I built the following little program on my mac with .NET 5  and it runs really fast (reported as 0 ms).  The data structure in my example, as you can see, is incredibly simple, so that might be the source of performance differences.  I'm also running on localhost, which could be different on your setup.
 

using System;
using InterSystems.Data.IRISClient;
using InterSystems.Data.IRISClient.ADO;

public class IRISNative
{
    public static void Main(String[] args) 
    {
        try {
            IRISConnection conn = new IRISConnection();
            conn.ConnectionString = "Server=localhost; Port=1972; Namespace=User; Password=...; User ID=...; SharedMemory=false; logfile=./dbnative.log";
            conn.Open();

            IRIS iris = IRIS.CreateIRIS(conn);

            Console.WriteLine("[1. Populating the data]");
            string global = "^testGlobal";
            object[] Subs = new object[1];
            Subs[0] = "node1";

            var watch = new System.Diagnostics.Stopwatch();
            watch.Start();
            for (var i=0; i<50; i++) {
                iris.Set(i, global, Subs[0], "node"+i);
            }
            watch.Stop();
            Console.WriteLine($"Execution Time: {watch.ElapsedMilliseconds} ms");

            Console.WriteLine("[2. Querying the data]");
            watch = new System.Diagnostics.Stopwatch();
            watch.Start();
            IRISIterator iter = iris.GetIRISIterator(global, Subs);
            foreach (var item in iter)
            {
                Console.WriteLine((string)(iter.CurrentSubscript));
            }
            watch.Stop();
            Console.WriteLine($"Execution Time: {watch.ElapsedMilliseconds} ms");

            iris.Close();
            conn.Close();
        }
        catch (Exception ex)
        {
            Console.WriteLine(ex.Message);
        }
    }
}
Bob Kuszewski · Feb 16, 2022 go to post

It runs in only 10 milliseconds (less if I don't actually print to console) on my machine.

But the time is nowhere near the 5 seconds in your original post, which is why I think we need to know more about your application.  If you take the same code as above what timing do you see?

Bob Kuszewski · Feb 25, 2022 go to post

docker-compose generates this error when ISC_IAM_IMAGE isn't set.  I have this problem when I forget to "source" the iam_setup.sh script in other words running the script via source exports the environment variables, but just running the script doesn't.
 

source ./scripts/iam-setup.sh
Bob Kuszewski · Mar 14, 2022 go to post

The IKO container is distributed as both part of the IKO distribution and via the InterSystems Container Registry.  For most users, the right answer is to just point to the container in ICR.  We mention this in the documentation here:  https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cl…

If you have your own container registry you can push the container there.  The error message provided looks like you're trying to add it to docker hub and getting permission denied. 

Bob Kuszewski · Mar 23, 2022 go to post

Yes, IKO provided support for a simple IRIS topology where all Compute (ECP clients) nodes are the same, as are all data (shards), and all web gateways.
IKO is a tool that simplifies common deployments of IRIS in Kubernetes.  It takes your description of your irisCluster and creates the base kubernetes objects needed to support that deployment (a real lifesaver for sharding/mirroring deployments).  You can always see what IKO created and use that as inspiration for creating your own YAML to deploy IRIS in your kubernetes environment.

Bob Kuszewski · Mar 30, 2022 go to post

I like to bake the timezone into the container when I build it.  That way it'll have the correct timezone no matter where I run it.  Here's an example Dockerfile based on the latest IRIS container that sets the container's timezone to Pacific (aka America/Los_Angeles).
 

FROM intersystemsdc/iris-community
USER root
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update && \
    apt-get install -yq tzdata && \
    ln -fs /usr/share/zoneinfo/America/Los_Angeles /etc/localtime && \
    dpkg-reconfigure -f noninteractive tzdata
USER irisowner

You can then do a docker build . to create the container, docker image ls, and docker run

Bob Kuszewski · Apr 20, 2022 go to post

In Embedded Python, exceptions flow back-and-forth between ObjectScript and Python as you'd expect. 

If your Python code raises an exception, but does not handle it, then the exception is passed to the ObjectScript side.  And vice-versa.  In your example, I'm not sure why you're handling the exception in python and then returning an exception object to the caller.  Why not just not catch the exception and let it get passed along to the ObjectScript side?

Bob Kuszewski · May 16, 2022 go to post

The OpenTelemetry collector should be able to collect metrics from the IRIS metrics API as well as the structured logs from the logdmn.  I don't have a working example configuration file to show you yet but I expect to have one by June 20th.  

As for a completely shameless plug here for my session on Observability in IRIS at Global Summit, I'm planning to cover the pillars of modern observability stacks, how IRIS fits into them.  At the moment, I'm still deciding which commercial stack to demo (DataDog, perhaps?).  I'll also be covering SAM, recent & future updates,  and how it fits into the bigger observability picture

Bob Kuszewski · Jun 3, 2022 go to post

Unfortunately, we do not have a workaround for Docker's breaking change included in 2022.1.  The instructions in my Docker post should still be followed.

Bob Kuszewski · Jun 6, 2022 go to post

As is our long standing practice, preview releases are taken down once a GA release is available.  We currently have the following versions available on IRC:  2019.1.3.722.0, 2020.1.3.521.0, 2021.1.2.338.0, 2021.2.0.651.0, 2022.1.0.209.0

Bob Kuszewski · Jun 6, 2022 go to post

Community images are published to DockerHub, as is the longstanding practice. Docker is currently semi-retiring their old "store" portion of DockerHub leaving a confusing interface to find our containers.  We expect that Docker will clear this up in the next few months.

In the meanwhile, you can easily find InterSystems community containers via the InterSystems Organization on DockerHub:

https://hub.docker.com/u/intersystems
 

Bob Kuszewski · Jun 6, 2022 go to post

containers.intersystems.com/intersystems/irishealth-ml:2022.1.0.209.0 is available on ICR, if that's what you're asking.  We didn't list every single container in the announcement because, well, there are a lot of them