Package Details: dgraph-bin 21.03.1-1

Git Clone URL: https://aur.archlinux.org/dgraph-bin.git (read-only, click to copy)
Package Base: dgraph-bin
Description: Fast, transactional, distributed graph database
Upstream URL: https://github.com/dgraph-io/dgraph
Keywords: dgraph
Licenses: Apache, custom:DCL
Conflicts: dgraph, dgraph-git
Provides: dgraph
Submitter: trengrj
Maintainer: wayfarer (kevorr)
Last Packager: wayfarer
Votes: 5
Popularity: 0.050914
First Submitted: 2016-10-25 07:58
Last Updated: 2021-06-25 05:05

Pinned Comments

wayfarer commented on 2021-05-25 07:39

Some pretty significant changes recently, so read carefully and don't be afraid to comment asking for clarification or offering suggestions. As of version 20.11.2-2 this package switches to using upstream's systemd service files instead of separate downstream versions. The new service files assume a different data directory path and use of a dgraph user, both of which are typically set up via upstream's add_dgraph_account.sh script. This script has been wrapped with the dgraph-bin.install file in this package to handle different cases, such as updating from the old service files to the new service files. The upstream dgraph-alpha service automatically starts the dgraph-zero service, so starting them both when they are initially down is as simple as systemctl start dgraph-alpha.

Additionally, upstream is moving away from including ratel releases with dgraph releases since ratel has now been open sourced in its own separate repository. As such, versions 21.03.0-1 and onwards of this package do not contain the dgraph-ratel binary and dgraph-ui.service file. Instead, they have been moved to a separate package which uses the upstream ratel releases. Note that the dgraph-ui service is not dependent on the other two, so you must specify the dgraph-alpha service if you wish to start all three services (systemctl start dgraph-alpha dgraph-ui).

Finally, version 21.03.0 marks the start of a new release series and thus contains breaking changes. When upgrading, please make sure to follow the dgraph documentation's recommendations; in particular, you should follow either the backup/restore or export/import process to transfer your data between major versions.

wayfarer commented on 2020-08-01 03:56

As of March 2020, dgraph has switched from semantic versioning to calendar versioning. Upstream will start a new release series every 4 months, and a release series will be supported for 12 months (security patches 18 months). As can be seen in the git log, I experimented with providing PKGBUILDs for the latest release in all currently supported series. I had hoped that the AUR server would rely on $pkgver in the PKGBUILD when offering the latest release, but it instead uses the latest commit. This will break new installations and upgrades of existing installations for any release series except the most recent release. Moving forward, I will only provide releases for the most recently created release series (i.e. 20.07 at this time until 20.11 is released and so on). This is in line with the Arch Linux Principles. If you wish to get a different version than the latest, download the PKGBUILD, change $pkgver, and proceed with building the package as normal. You can also follow the standard downgrade guidelines provided in the wiki.

Latest Comments

wayfarer commented on 2021-06-10 08:58

You're welcome and thanks for the feedback! Your observation is correct, so I updated my pinned comment accordingly.

wayfarer commented on 2021-05-25 07:39

Some pretty significant changes recently, so read carefully and don't be afraid to comment asking for clarification or offering suggestions. As of version 20.11.2-2 this package switches to using upstream's systemd service files instead of separate downstream versions. The new service files assume a different data directory path and use of a dgraph user, both of which are typically set up via upstream's add_dgraph_account.sh script. This script has been wrapped with the dgraph-bin.install file in this package to handle different cases, such as updating from the old service files to the new service files. The upstream dgraph-alpha service automatically starts the dgraph-zero service, so starting them both when they are initially down is as simple as systemctl start dgraph-alpha.

Additionally, upstream is moving away from including ratel releases with dgraph releases since ratel has now been open sourced in its own separate repository. As such, versions 21.03.0-1 and onwards of this package do not contain the dgraph-ratel binary and dgraph-ui.service file. Instead, they have been moved to a separate package which uses the upstream ratel releases. Note that the dgraph-ui service is not dependent on the other two, so you must specify the dgraph-alpha service if you wish to start all three services (systemctl start dgraph-alpha dgraph-ui).

Finally, version 21.03.0 marks the start of a new release series and thus contains breaking changes. When upgrading, please make sure to follow the dgraph documentation's recommendations; in particular, you should follow either the backup/restore or export/import process to transfer your data between major versions.

wayfarer commented on 2021-03-23 03:42

@galaux thanks for pointing that out, I plan to switch when I return to a non-metered internet connection soon. The upstream-provided files look rational at a glance, though I'll test what the transition to a dgraph system user is like before I push anything.

galaux commented on 2021-03-19 13:17

Thanks for this package. Just wanted to highlight that upstream already provides Systemd files.

wayfarer commented on 2020-12-16 20:32

Note that v20.11 includes a breaking change from v20.07 to use a newer version of badger (the underlying key-value database for dgraph) with a new Write-Ahead Log format. If you get the "manifest has unsupported version: X (we support Y)" error upon upgrading and then starting the dgraph-ratel service, either backup then restore or export then import your data from dgraph, making sure to clear out the data directory (/var/lib/dgraph/data/) between steps.

wayfarer commented on 2020-08-01 03:56

As of March 2020, dgraph has switched from semantic versioning to calendar versioning. Upstream will start a new release series every 4 months, and a release series will be supported for 12 months (security patches 18 months). As can be seen in the git log, I experimented with providing PKGBUILDs for the latest release in all currently supported series. I had hoped that the AUR server would rely on $pkgver in the PKGBUILD when offering the latest release, but it instead uses the latest commit. This will break new installations and upgrades of existing installations for any release series except the most recent release. Moving forward, I will only provide releases for the most recently created release series (i.e. 20.07 at this time until 20.11 is released and so on). This is in line with the Arch Linux Principles. If you wish to get a different version than the latest, download the PKGBUILD, change $pkgver, and proceed with building the package as normal. You can also follow the standard downgrade guidelines provided in the wiki.

wayfarer commented on 2020-06-05 01:21

Sure thing! I'm fine with that. I also just now realized that you can set up email release notifications on github so I followed the upstream git repo and that should help with more timely updates as well.

jnylen commented on 2019-04-15 02:16

@kjnsn, Can you disown the package or update it?

shadow79 commented on 2017-03-18 14:43

Updated PKGBUILD:

http://pastebin.com/k3wJeiYz

Updated dgraph.service:

http://pastebin.com/3srr1Gj3