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
Linux 6.6.16-linuxkit - OpenJDK 64-Bit Server VM 11.0.22 (Temurin-11.0.22+7)
(docker image)
Expected behavior
exported database cannot be imported
Actual behavior
exported database should be imported
Steps to reproduce
create a database (e.g test) and build a simple graph (any graph is fine, it seems has nothing to do with the content)
export the database test with command: EXPORT DATABASE file://test.jsonl.gz OVERWRITE true
just drop and recreate the test database。
import file into current test database with command: IMPORT DATABASE file://exports/test.jsonl.gz WITH database = 'test'
after the import operation, test database ends with NOTHING inside...
SOME REMARK
I clone the source and try debug, it seems that the implementation of importers are all about import format from other kind of databases and never handles arcadedb's own format. seems to be a missing feature?
The text was updated successfully, but these errors were encountered:
ArcadeDB Version:
tried with
24.2.1
,24.1.1
,23.12.1
OS and JDK Version:
Linux 6.6.16-linuxkit - OpenJDK 64-Bit Server VM 11.0.22 (Temurin-11.0.22+7)
(docker image)
Expected behavior
exported database cannot be imported
Actual behavior
exported database should be imported
Steps to reproduce
test
) and build a simple graph (any graph is fine, it seems has nothing to do with the content)test
with command:EXPORT DATABASE file://test.jsonl.gz OVERWRITE true
test
database。test
database with command:IMPORT DATABASE file://exports/test.jsonl.gz WITH database = 'test'
test
database ends with NOTHING inside...SOME REMARK
I clone the source and try debug, it seems that the implementation of importers are all about import format from other kind of databases and never handles arcadedb's own format. seems to be a missing feature?
The text was updated successfully, but these errors were encountered: