atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Graham Wallis (JIRA)" <>
Subject [jira] [Commented] (ATLAS-2084) Make berkeley DB backed Atlas available without external download
Date Tue, 21 Nov 2017 09:59:00 GMT


Graham Wallis commented on ATLAS-2084:

The berkeley jar is pulled in by the janusgraph provider but is currently being specifically
excluded by the Atlas build (see webapp/pom.xml 'dist' profile) if building a standalone package.
That will be rectified soon, subject to ATLAS-2270.

> Make berkeley DB backed Atlas available without external download
> -----------------------------------------------------------------
>                 Key: ATLAS-2084
>                 URL:
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Nigel Jones
>            Assignee: Nigel Jones
>         Attachments: ATLAS_2084_Add_BerkeleyDB_libraries.patch
> In I proposed providing a dockerized
version of Atlas to aid people getting up to speed with the technology. During the review
it was noted that we had used Hbase for storage rather than the more lightweight, simpler,
BerkeleyDB. My concern had been around licensing.
> Today when we build Atlas following the instructions at
the user is directed to download the berkeleyDB jar from oracle. In ATLAS-2012 David/Graham
pointed out that this DB appears to be Apache 2.0 licensed, which means we could incorporate
it into our build legitimately.
> Given the necessity to get licensing correct I've opened up this new JIRA to focus on
that change. We would need to
>  * Validate we are indeed correct about the license
>  * Add the DB file into the build
>  * Update the web instructions
>  * And optionally as per the original JIRA, consider making B-DB the default for our
docker image (most lightweight).
> Please add your thoughts. I'm happy to get and do this change .

This message was sent by Atlassian JIRA

View raw message