Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

OrientDB fails to import this export [moved] #900

Closed
lvca opened this Issue · 1 comment

1 participant

@lvca
Owner

This is Issue 900 moved from a Google Code project.
Added by 2012-06-15T18:45:57.000Z by ndari...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.

Original labels: Type-Defect, Priority-Medium, Release

Original description

<b>OrientDB release? (If you're using a SNAPSHOT please attach also the build</b>
number found in &quot;build.number&quot; file): 12092


<b>What steps will reproduce the problem?</b>
1. Import the attached database dump.
2. After connecting to the database, run &quot;select changes.size() from Script&quot;

<b>If you're using custom settings please provide them below (to dump all the</b>
<b>settings run the application using the JVM argument</b>
<b>-Denvironment.dumpCfgAtStartup=true):</b>


<b>What is the expected output? What do you see instead?</b>

I would expect to see a bunch of 1s and a 2, but instead I see all 0s.

<b>If you're describing a performance or memory problem the profiler dump can</b>
<b>be very useful (to dump it run the application using the JVM arguments</b>
<b>-Dprofiler.autoDump.reset=true -Dprofiler.autoDump.interval=10</b>
<b>-Dprofiler.enabled=true):</b>


<b>Please use labels and text to provide additional information.</b>

OrientDB seems to fail to import this dump, which includes embedded lists of empty strings. It could be that my export is broken too, but I don't know how to easily package a binary database for investigation. Either way, this bug blocks my ability to move an app to production since I can't easily just copy a binary database to my production server.

Thanks.
@lvca
Owner

This is pretty old. Closing it.

@lvca lvca closed this
@lvca lvca added the bug label
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.