snowstorm
snowstorm copied to clipboard
IHTSDO
FULL Import Failure on Snowstorm 9.2.0
Hi, I am experiencing a problem when trying to upload the full version of SNOMED CT using Snowstorm version 9.2.0:
java -Xms2g -Xmx4g -jar snowstorm-9.2.0.jar --delete-indices --import-full=SnomedCT_InternationalRF2_PRODUCTION_20230901T120000Z.zip
The upload process fails, and the following error is logged:
FULL import is only implemented for the MAIN branch and when there is no existing content.
Environment
- Snowstorm Version: 9.2.0
- Elasticsearch Version: 7.17.16
- Java Version: 17
- OS: Windows 11
I'm wondering if there's a workaround or a fix that I might have missed. Any pointers or guidance would be greatly appreciated!
Best regards, Eirik
@eiriknicholas This bug is fixed in develop (https://github.com/IHTSDO/snowstorm/commit/32b83f4e122e47ed9e7849eb1cf5161ce360a9a8). Unfortunately in 9.2.0 you can use --import option for snapshot import only. Note ES8 is required if you use develop branch.
Thank you so much, @CoderMChu ! We'll try to run a test using the develop branch.
That said, we're not going to production with something build on a dev-branch for our customers:) Do you have an (gu)estimate for when this fix will be pulled into master?
Best from Oslo, Norway,
(another) Eirik
@eirikconteir It will be towards the end of February next year unfortunately.
@eirikconteir For a workaround you can update containsContent=false for the latest MAIN branch document via kibana before full import and set it to true afterwards.
Thanks a lot, @CoderMChu ! If a production installation is urgent, we'll go with the workaround. If not, we patiently wait:)
This issue is from our perspective closed. Again, thank you so much for your support!
Hi again, @CoderMChu ! After upgrading to 10.1 FULL import works:)
But another issue appeared for the browser: After creating a third level code system (MAIN/SNOMEDCT-NO/CONTEIR) the browser stoped working
Does this make any sense to you?
@eirikconteir Sorry to hear that you have got another issue. The error seems to be related to ecl-builder-ui component. Can you please raise an issue in https://github.com/IHTSDO/ecl-builder-ui? Thanks.