Drop all partially works for schema


For my tests I use the {DropAll: true} alteration with the go client at the beginning of my tests, the I set the schema. Works fine with the tests, also data and schema are as expected when I look them from ratel.

But each time I run my tests, it adds a new bulk of:

2018/09/08 12:09:00 mutation.go:141: Done schema update predicate [...]

to the logs of the dgraph server.

So let’s say my schema has 10 indexes defined, so after running 10 times my tests, when I start the dgraph test server I get 100 “update predicate” lines in my log.
And of course it slows progressively the starting of the dgraph test server.

If I remove the data folders, it clears that aggregation but after that it keeps growing again.

The solution is simple, use “-s schema.schema” in BulkLoad in the first setup.
In other bulkloads do not use the flag -s.

Sorry but this is not a bulk load, I just start the server normally with a supposedly empty database

All ten times you do your tests, do you clean the Dgraph?

Yes. As I said, I systematically do a drop all and then an alter schema at the beginning of my tests.
In ratel, the database is fine: No data, schema well defined.
But when I start the server, the schema seems to be duplicated as many times as I launched my tests. According to the logs anyway

This looks like a bug. Can you file an issue on GitHub?

I cannot reproduce it anymore.
If it ever happens again, I’ll submit an issue.

Problem still here, but I cannot produce a basic program that reproduces it.
When I run my tests with a count=10 for instance, each time I run them again the total time increases because of that, but it doesn’t influence the test results.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.