-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Datastore - Failed to load from the backing store - java.lang.ClassNotFoundException: com.google.cloud.datastore.emulator.impl.LocalDatastoreFileStub #4661
Comments
Hi @ajaaym,
|
@ajaaym - I'm a colleague of @andrewcampey. Full details of the process we're currently following and the location that we're using for the local_db.bin file is documented in my StackOverflow answer here - https://stackoverflow.com/questions/55037520/app-engine-localdatastoreservice-load-failed-to-load-from-the-backing-store/55465569#55465569 Also, we currently use Firebase for hosting our primary web application. I'm not sure if our setup is utilising 'Cloud Firestore in Datastore mode' though (as described here - https://cloud.google.com/datastore/docs/activate#google_cloud_datastore_for_an_existing_app_engine_application) |
@chalcrow I am not able to find the required class |
Thanks @ajaaym - I updated to the following dependencies in our pom.xml - same error occurs:
Here's our full pom.xml Note that it contains the following dependency (with test scope only) - however if I remove this, clean and rebuild we still have the same error:
|
@chalcrow @andrewcampey , I am sorry for your issue. Though this doesn't seem to involve the Java Client Library. This issue seems to be related to datastore and the emulator. Could you please file your issue on the Cloud Datastore issue tracker: https://issuetracker.google.com/issues/new?component=187197&template=1162794 |
We are hitting a brick wall with trying to use our local datastore.
We can export successfully and the import creates a local_db.bin that LOOKS correct however when we try and connect to it we hit the error mentioned below.
If we stop and re-run our local environment it will blow this file away and start again.
Environment details
Steps to reproduce
Code example
POWERSHELL SCRIPTS
Export
Import
Stack trace
The text was updated successfully, but these errors were encountered: