FAQ: Broken Elasticsearch Head Chrome Extension Workaround
FAQ relevant for: all Academy versions Hi all, Support for Manifest V2 has officially been disabled in Google Chrome, which means the Elasticsearch Head Chrome extension is no longer functioning properly on the VDIs. When you try to add the Elasticsearch Head Chrome extension you may see the following error: "This extension was turned off because it is no longer supported" or this error: "Cannot install extension because it uses an unsupported manifest version. Could not load manifest." We are looking into ways we can resolve this issue, however for now we have a workaround to get the extension working. Latest Workaround Step 1: Go to the Ubuntu terminal and run the following command: nano ~/Desktop/chrome-v2.desktop Step 2: Enter the following and save the changes: [Desktop Entry] Version=1.0 Type=Application Name=Chrome (Manifest V2 Enabled) Comment=Run Google Chrome with Manifest V2 enabled Exec=/usr/bin/google-chrome-stable --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled Icon=google-chrome Terminal=false This will create a new shortcut for Google Chrome which should allow you to add and use the Elasticsearch Chrome extension! (Old) Workaround Here are the steps you can follow to work around this error: Step 1: Navigate to chrome://flags/ in the Chrome browser: Step 2: Disable the following settings: Extension Manifest V2 Deprecation Warning Stage Extension Manifest V2 Deprecation Disabled Stage Extension Manifest V2 Deprecation Unsupported Stage Alternatively on some versions the setting may appear as the following: Allow legacy extension manifest versions In this case you will need to enable the setting as seen above. Step 3: Restart Chrome. Step 4: Re-add the Elasticsearch Head Chrome extension. This comment details how to add the extension to Chrome. You should now be able to use the Elasticsearch Head Chrome extension as normal! Alternative Elasticsearch Query Tool Alternatively you can query your Elastic indices without using the Elastic head Chrome extension! This post walks you through this method: ElasticSearch alternative query tool | Quantexa Community Thanks pashadia for creating this post! Apologies for the inconvenience, I hope this helps!New Elasticsearch Chrome Extension
Hi All, As you may have seen in FAQ: Broken Elasticsearch Head Chrome Extension Workaround the Elasticsearch extension we were using in the VDIs (Elasticsearch Head) is no longer supported by Google Chrome! We have now added a new extension called Multi Elasticsearch Heads to the VDIs to hopefully replace the old extension! This extension should both appear and function very similarly to Elasticsearch Head; however, if you are having any issues or have any questions on how to use the new extension, please let us know in the comments! How to add the new extension Step 1: To add the new extension, first you will need to run the following commands: cd ~ cp /opt/training/other-resources/chrome-plugins/ElasticMultiheadChrome.zip ~ unzip ElasticMultiheadChrome.zip -d ElasticMultiheadChrome Step 2: Open up files and navigate to the "Home" folder You should now see a folder called ElasticMultiheadChrome Step 3: Add the new extension to Chrome To do this you can either follow the instructions in the environment setup module or follow the guide in this comment! Remember to select the ElasticMultiheadChrome folder instead of the elastic_head folder! Step 4: Done! You should now be able to use the new extension! I hope this helps, and please let us know if you have any issues etc!
FAQ: Elasticsearch "cluster health: Not connected" in Chrome / "Connection refused" script error
FAQ relevant for: all Academy versions Sometimes on the VDIs you will encounter your Elasticsearch being disconnected which will then mean that the data isn't available for easy viewing and it will also lead to errors in your UI. If you try to run e.g. a load Elastic ETL script while Elastic isn't connected then you will get an error, for example: Exception in thread "main" java.net.ConnectException: Connection refused To reconnect the Elasticsearch service you just need to run the following command anywhere in a terminal window on your VDI: sudo systemctl restart elasticsearch.serviceFAQ: I'm missing data in Elasticsearch / my number of docs are wrong
FAQ relevant for: all Academy versions If you have completed the ETL pipeline stages of your project and uploaded the data to ElasticSearch, then when checking your indices in the ElasticSearch Head plugin on Chrome you should have numbers similar to the picture below (to get a bigger version of the image, right click it and chose the option to open it in a new tab). Note: If your numbers vary a little bit from these, for example having 152k address instead of 148k, then that's ok - the numbers will change a little for the resolver indices (Individual/Address/Business) based on the compound keys you have imported in the respective *.qentity Fusion config files. If your numbers are significantly different to this, then you will want to go back through your ETL pipeline and carefully check each stage to see if there is somewhere that you lose the data along the way. A good way to approach this problem is to work forwards from CreateCaseClass and check the output of each stage to find the problem area. You should also use the counts in ElasticSearch to guide you - for example if you have only half the number of businesses listed above, and no individuals, it lets you know that you probably haven't joined your Third Parties onto the ICIJ document properly, and so you would want to go back and double check how you have done this join and on what fields. Specific points to consider: Have I correctly parsed all of the necessary fields in my qmodel files? Have I used the correct type of joins in CreateCaseClass, and have I joined on the correct fields? Have I outputted the correct Dataset at the end of CreateCaseClass? Have I loaded up the DocumentDataModel.parquet (the output of CreateCaseClass) into a Spark-Shell to check the output there? Have I correctly identified and defined all relevant start paths in my qentity files? Do I have a good range of compound keys for each Entity? If you are convinced that you have done all of the above correctly then you can try to clear the data from ElasticSearch, restart the service and then re-upload the data to Elastic using the following three commands: curl -X DELETE 'http://localhost:9200/_all' sudo systemctl restart elasticsearch.service ./runQSS.sh -s com.quantexa.academy.task.icij.model.etl.IcijLoadElasticScript -c ../external.conf -r elastic.icij
