You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if your team @hannahbast have thought about the possibility to use qlever-control to rebuild an index inside a running qlever container (without container stopping)? Maybe add a REST API (POST file1.nt, file2.nt) to qlever endpoint s.t. new index can be build without shutting down the container. This would make it possible to run it with cubernetes, which is my use-case.
Love the work you/your team have done with this engine btw :) !
The text was updated successfully, but these errors were encountered:
@PetterBMarkussen Sorry for not having responded earlier, we overlooked this. Is this still relevant? And do I understand you correctly, that the issue is not that you want SPARQL 1.1 Update functionality, but that you would be fine with rebuilding the index, as long as it can all take place in the same container? The latter can be achieved already now and I wonder what exactly your problems were if any.
Hi,
I was wondering if your team @hannahbast have thought about the possibility to use qlever-control to rebuild an index inside a running qlever container (without container stopping)? Maybe add a REST API (POST file1.nt, file2.nt) to qlever endpoint s.t. new index can be build without shutting down the container. This would make it possible to run it with cubernetes, which is my use-case.
Love the work you/your team have done with this engine btw :) !
The text was updated successfully, but these errors were encountered: