The extension uses the org.apache.parquet library and writes the parquest file to Thingworx repositories. The service works correctly if Thingworx is installed on a Virtual machine. The service fails to write the file to Thingworx repositories if Thingworx is installed on kubernetes containers. In particular the extension fails by going to do a chmod 644 on the file to define the correct privileges. Has anyone had the same problem? Are there any solutions to the problem?
Thanks
Dimitri
Solved! Go to Solution.
Hi @dbologna
Per the case you opened, you were able to develop a new extension for resolving your issues. If you would like to share more information regarding your fix, please feel free to post it here.
Regards.
--Sharon
This seems specific to how the ThingWorxStorage PVC is mounted in the PTC Cloud. We are aware that you have opened a case and are currently investigating.
Hello Dimitri,
Just a guess -- some k8s implementations (notably Openshift) do not grant container user root permissions. I guess you mount /ThingworxStorage as a Persistent Volume. In this case you need to specify user IDs explicitly on your pods and volumes, to grant non-root users write access to such mount, as described here.
Also, a pretty obvious tip -- try to log into ThingWorx pod and check permissions on the /ThingworxStorage/repository directory itself.
/ Constantine
Hi @dbologna
Per the case you opened, you were able to develop a new extension for resolving your issues. If you would like to share more information regarding your fix, please feel free to post it here.
Regards.
--Sharon