Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client configuration #58

Open
Mec-iS opened this issue Dec 5, 2018 · 2 comments
Open

Client configuration #58

Mec-iS opened this issue Dec 5, 2018 · 2 comments

Comments

@Mec-iS
Copy link
Contributor

Mec-iS commented Dec 5, 2018

There should be a flawless way for configuring the client so the user, at deploy-time, can define:

  • structure of the indexes
  • ...
@knakul853
Copy link

@Mec-iS can you please elaborate the issue

@Mec-iS
Copy link
Contributor Author

Mec-iS commented Dec 11, 2018

the developer should be allowed to configure how the local graph is indexed and other options. So for every entrypoint he/she should be able to define a data structure in which the configuration is stored. Every time the client instance is created, the code should read the data structure and set up the client in the way defined by the user (rebuild the indexes, etc).
Example of a structure to configure a faceted index on a property:

{
"http://somedomain/vocab" : {
    "graph": {
            "indexing": {
                   "faceted": [
                         {
                               "resource": "<HydraClass>",
                               "property": "<property to index>"
                          }
                    ]
             }
        }
    }
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants