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

Q: BlazeGraph to GraphdB #570

Open
priya-gitTest opened this issue Sep 24, 2024 · 3 comments
Open

Q: BlazeGraph to GraphdB #570

priya-gitTest opened this issue Sep 24, 2024 · 3 comments

Comments

@priya-gitTest
Copy link

priya-gitTest commented Sep 24, 2024

Do you provide any guidance on how to move from BlazeGraph to GraphdB ?
Considering Blazegraph is sold to Amazon

@priya-gitTest priya-gitTest changed the title BlazeGraph to GraphdB Q: BlazeGraph to GraphdB Sep 24, 2024
@xiaofengleo
Copy link

https://fairdatapoint.readthedocs.io/en/latest/deployment/advanced-configuration.html
section 4. GraphDB

@priya-gitTest
Copy link
Author

Getting this error :
image
image

@CAVDgit
Copy link

CAVDgit commented Oct 25, 2024

If you access the FDP client, you may see an error message saying "unable to get data." This is likely the same error appearing in the logs. This error is expected, as the GraphDB repository specified in application.yml has not yet been created.
You need to create it manually.

To create the repository, access the GraphDB interface on port 7200: Example: http://localhost:7200/

Click on "Add repository."
Set the name to match the one defined in application.yml, then save.
After a few seconds, the FDP should operate without errors, allowing you to create records.

Also when (re)booting the whole docker compose, the GraphDB instance takes more time to setup (>15-30sec) than Blazegraph (at least from my side). During that time, you may expect again "unable to get data." in the FDP client. You just have to wait GraphDB fully start.

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

No branches or pull requests

3 participants