-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Orientdb cleanup #586
Orientdb cleanup #586
Conversation
dictionary = db.getMetadata().getIndexManager().getDictionary(); | ||
if (!db.getMetadata().getSchema().existsClass(CLASS)) { | ||
db.getMetadata().getSchema().createClass(CLASS); | ||
} | ||
|
||
db.declareIntent(new OIntentMassiveInsert()); | ||
if (intent.equals(ORIENTDB_MASSIVEINSERT)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should these be set automatically per type of action? Like insert should be massiveinsert, read should be massiveread, etc? Or is it assumed that these settings will be set when someone runs a workload?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I don't think they should be set automatically, that is actually why I moved this to a user property. It is an optimization, not a necessary action. Prior to this change MassiveInsert was being set no matter what which didn't much make since for workloads that weren't inserting.
👍 looks good to me. |
Orientdb cleanup
Orientdb cleanup
Two things fixed here: