Skip to content

[BUG]: Dgraph should correctly export data from a shared instance(ACL). #8402

@MichelDiz

Description

@MichelDiz

What version of Dgraph are you using?

latest

Tell us a little more about your go-environment?

N/A

Have you tried reproducing the issue with the latest release?

No response

What is the hardware spec (RAM, CPU, OS)?

N/A

What steps will reproduce the bug?

Create a shared instance in the Cloud.
Then add data. Then export them.
Then open RDF and Schema in a text editor and you will see that the data comes with namespace context.

Expected behavior and actual result.

The expected result was that Dgraph exported the Schema and RDF cleanly. No ACL context.

In short, as it is a shared instance. The namespace context is irrelevant. Because if the user is exporting it, he will certainly load it into a new instance. And if it loads into a new shared instance, it can't choose which namespace it will have. Because he is not general admin.

We have two options.

Or add a way to ignore namespaces (and predicates for namespaces during mutation) in liveload and bulkload.

Or do not export any namespace and ACL data. Have an option to export clean.

Additional information

https://discuss.dgraph.io/t/live-loader-option-to-skip-unauthorized-predicates/17929/7?u=micheldiz

Metadata

Metadata

Assignees

No one assigned

    Labels

    Stalearea/aclRelated to Access Control Listsarea/enterpriseRelated to proprietary featuresarea/import-exportIssues related to data import and export.dgraphIssue or PR created by an internal Dgraph contributor.dgraph/cloudkind/bugSomething is broken.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions