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
Is your feature request related to a problem? Please describe the problem.
No response
Describe the solution you'd like
I'd like the Lucene.Net.Store.Azure.AzureDirectory to be enabled for usage with sasuri with existing containers instead of using the storage account connectionstring. Reason: to constrain access to containers for multiple usages on the same storage account.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hi, Lucene.Net.Store.Azure.AzureDirectory is a 'dead' library and isn't maintained. Much of it has been forked in various repos and attempted to be updated to work. Most people don't fully understand what is actually does though:
What is doesn't do:
It does not allow you to share indexes between processes
What it does do:
It 'syncs' the lucene files from a central storage (i.e. Blob Storage) to local storage of the current process (i.e. %temp%) folder
It attempts to keep both the local storage and central storage in sync
When an Azure App Service using this library is moved to another worker, it will re-sync the main storage to local storage in an attempt to keep working as it was on the previous worker
The lib isn't maintained because this underlying process has several issues because depending on the index activity, writing this much to blob storage and local storage and keeping it in sync is difficult and can easily cause index corruption issues.
This doesn't use Blob storage, but just the main file system in Azure App Service (which is a network drive) and syncs to the local %temp% file system.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
No response
Describe the solution you'd like
I'd like the Lucene.Net.Store.Azure.AzureDirectory to be enabled for usage with sasuri with existing containers instead of using the storage account connectionstring. Reason: to constrain access to containers for multiple usages on the same storage account.
Additional context
No response
The text was updated successfully, but these errors were encountered: