go to post Benjamin De Boe · Jan 3, 2022 Thanks @Kevin Chan for helping out (he's the author of the parser piece of LOAD DATA ;-) ) In addition to his comments on the encoding issues, you can also take a look at the %SQL_Diag.Result table which will likely have more detailed error info than what we're able to return through SQL semantics (though we're still working on ways to make it clearer). There's also a %SQL_Diag.Message table with row-level errors, which can help you figure out the reason for individual row failures.
go to post Benjamin De Boe · Jan 3, 2022 You can configure your Java Gateway's JVM arguments through the [Gateways] section in the CPF file or, preferably, through the API documented here
go to post Benjamin De Boe · Dec 29, 2021 Congratulations! We're lucky to have airpods as the third place prize. Those were easy to split equally between the tied contestants :-)
go to post Benjamin De Boe · Dec 17, 2021 This sounds exciting! Do you have a demo video, screenshots or a link to the full product page to make it more tangible?
go to post Benjamin De Boe · Dec 15, 2021 Correct. We can only use this for classes using %Storage.Persistent (and %Storage.Shard), because of the wildly varying structures (not least involving multiple globals) you might project using alternative models.
go to post Benjamin De Boe · Dec 14, 2021 Here are two examples using Synthea: https://github.com/intersystems-community/irisdemo-base-synthea https://github.com/grongierisc/synthea-fhir-iris And two example repositories using LOAD DATA (but not yet ZPM-enabled): https://github.com/bdeboe/isc-tpch-script https://github.com/bdeboe/isc-adventureworks (using the DWH flavour of this well-known dataset only)
go to post Benjamin De Boe · Dec 6, 2021 See also this DC article about the subject. What exactly do you want to "switch back" and why?
go to post Benjamin De Boe · Nov 13, 2021 an iFind transformation would be helpful if you would sometimes want to query the non-transformed form as well, which I don't think is the case here. Just a computed field and/or @Timothy Leavitt s excellent BuildValueArray() sample would be a simple and effective solution.
go to post Benjamin De Boe · Nov 13, 2021 hmm, I believe that's a feature of DocDB that crept into the wrong (or at least a confusing) part of the documentation. I'll follow up internally. Thanks for the note.
go to post Benjamin De Boe · Sep 21, 2021 Of course it's just one approach to the problem but I hope it can be helpful. Stay tuned for a dedicated LOAD DATA command in IRIS SQL coming very soon :-)
go to post Benjamin De Boe · Jul 29, 2021 The iFind search portal demo includes a simple class query to find similar documents within a single iFind index. It's only pretty basic and somewhat picky (assuming the demo setup), building on the dominance score for each entity, and may not guard against that difference in length issue you're seeing with BM25. There is a similar method in iKnow when your data would already be in an iKnow domain. There would indeed be value in providing %SIMILARITY support for iFind indexed fields, leveraging the standard/enhanced algorithm on top of word tokens. I'll log that as an enhancement request and we can follow up internally. Obviously, I'm interested in experiences or advice of other DC members here
go to post Benjamin De Boe · Jun 21, 2021 yes, they are the same. Like Studio and ODBC, it's an install-time option to right-size your footprint (and therefore highly relevant for container images). I'm not sure if there's a handy utility method to check if it's been installed or not, but @Thomas Dyar would know.
go to post Benjamin De Boe · Jun 17, 2021 Yes. If you navigate to the WRC software distribution site or even just https://download.intersystems.com/, you can select community edition kits for a variety of platforms, including Windows.
go to post Benjamin De Boe · Jun 17, 2021 You're spot on. The similarity between Python and ObjectScript plus its popularity (Python's, that is ;-) ) are exactly what drove us to build Embedded Python. We're not compiling it to .obj code though, but running it "as Python" in the kernel. @Bob Kuszewski and @David McCaldon are much better at explaining that nuance (and actually do in the intro webinar to our early access program for this upcoming feature.
go to post Benjamin De Boe · Jun 17, 2021 Hi Nigel, glad you like the Python Gateway work. Perhaps you're also interested in participating in the embedded python EAP? As for APL, we're typically looking for some critical mass of customer demand before embarking on such a development project and only recall it being mentioned once before. But thanks for bringing it up, as each critical mass starts somewhere :-). This said, we've had some really great work pioneered in the community here. The Python Gateway project is one example that originated here and its popularity (thanks @Eduard Lebedyuk and @Sergey Lukyanchikov !) inspired the one now released as part of the core InterSystems IRIS platform. Similar concepts, such as the Julia Gateway are still "incubating" as a community-driven project. Maybe APL could fit that same path?
go to post Benjamin De Boe · Jun 17, 2021 I believe the R one goes through the Java gateway, but not sure why it's not described (yet) in the docs. Pinging @Bob Kuszewski for more detail
go to post Benjamin De Boe · Jun 16, 2021 I think you're looking for this. The doc is not separate for each language, but the quick reference in the last section points you at the respective class references.
go to post Benjamin De Boe · Jun 15, 2021 Yes to both questions: For a full list of the available images, please refer to the ICR documentation. Our doc team is updating that page today, but generally anything for which there was a 2021.1.0.205.0 tag, there should also be a 2021.1.0.215.0. There were a few open questions on the new permutations that we were looking through this morning.
go to post Benjamin De Boe · May 3, 2021 Thanks for bringing it up. This had already been fixed in our working branch, but the fact that the port to 2021.1 was missing unfortunately escaped our automated tests. The fix will obviously be in the GA release, but we might publish another preview build before then to pick up this fix.
