[
https://issues.apache.org/jira/browse/ATLAS-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374297#comment-16374297
]
David Radley commented on ATLAS-2270:
-------------------------------------
Hi Pierre,
Great; you ask to be a contributer on the dev list - this allows you to
assign a Jira to yourself.
Then you create a patch in git and attach it to the Jira and put it into
the review board for review. There may be review comments or a "ship it".
After that a committer (probably me in this case) should take your patch
and push it to master.
I was new to git and have created a wiki page with the git commands I use
https://cwiki.apache.org/confluence/display/ATLAS/Using+Git+with+Atlas.
You may find this useful if you have not used git too much.
There is a also a wiki page for committers
https://cwiki.apache.org/confluence/display/ATLAS/Developer+Resources you
may be interested in .
I suggest that the Jira should be scoped just to the fix you want to put
in. You could change the words of 2270 or create a new one,
all the best, David.
From: "Pierre Padovani (JIRA)" <[email protected]>
To: [email protected]
Date: 22/02/2018 16:44
Subject: [jira] [Commented] (ATLAS-2270) Supported combinations of
persistent store and index backend
[
https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ATLAS-2D2270-3Fpage-3Dcom.atlassian.jira.plugin.system.issuetabpanels-3Acomment-2Dtabpanel-26focusedCommentId-3D16373048-23comment-2D16373048&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=QhpUQPr5YlG95aAgCvZGStEXHg4hBbSYQ9JkRqR_svY&m=XQ5cRTBSZfDIanJGha8zM6Dkgnw0IjOYn8x5TlzRFBc&s=CvAzKNiTZy_yOqiqGZadB1tR74aieY28pWb2P8q3ucI&e=
]
Pierre Padovani commented on ATLAS-2270:
----------------------------------------
[~davidrad] I'd be happy to be a contributor and get this in. How does one
go about becoming one? Are there a set of guidelines somewhere specific to
this project?
We've been running the Cassandra + ES 5.x flavor of Atlas as both a self
contained docker container for dev purposes, as well as a full blown HA
cluster for at least the last two months. So I think it looks like a
pretty stable setup.
https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ATLAS-2D2270&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=QhpUQPr5YlG95aAgCvZGStEXHg4hBbSYQ9JkRqR_svY&m=XQ5cRTBSZfDIanJGha8zM6Dkgnw0IjOYn8x5TlzRFBc&s=r6UWXjJszzenyZwhDWtpds09zR_aEaPTnA245uXb-vU&e=
indexing backend Atlas 1.0.0 (master) should support. This includes
building/running Atlas as a standalone package and running UTs/ITs as part
of the Atlas build.
databases that will be supported in master/1.0.0. This JIRA deliberately
ignores titan1 and janusgraph 0.1.1 as the former should be
deprecated/removed and the other is a transient state as we get to
janusgraph 0.2.0.
combinations of persistent store and indexer. It is suggested that this
set is kept unchanged:
additional combinations. Cassandra is included in this discussion pending
response to ATLAS-2259.
continued and the remaining 4 combinations, marked with '?', should be
considered. There seems to be evidence of people using all 4 of these
combinations, although not necessarily with Atlas.
possible to build Atlas as a standalone package with any of the
combinations - i.e. that they are mutually exclusive and do not interfere
with one another. They currently interfere which makes it impossible to
build Atlas with -Pdist,berkeley-elasticsearch because the 'dist' profile
will exclude jars that are needed by the berkeley-elasticsearch profile -
which leads to class not found exceptions when the Atlas server is
started. The solution to this could be very simple, or slightly more
sophisticated, depending on how many of the combinations we choose to
support.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
> Supported combinations of persistent store and index backend
> ------------------------------------------------------------
>
> Key: ATLAS-2270
> URL: https://issues.apache.org/jira/browse/ATLAS-2270
> Project: Atlas
> Issue Type: Bug
> Reporter: Graham Wallis
> Priority: Major
>
> We need to discuss and decide which combinations of persistent store and
> indexing backend Atlas 1.0.0 (master) should support. This includes
> building/running Atlas as a standalone package and running UTs/ITs as part of
> the Atlas build.
> This JIRA focusses on titan0 and janusgraph 0.2.0, as they are the graph
> databases that will be supported in master/1.0.0. This JIRA deliberately
> ignores titan1 and janusgraph 0.1.1 as the former should be
> deprecated/removed and the other is a transient state as we get to janusgraph
> 0.2.0.
> With titan0 as the graph provider, Atlas has supported the following
> combinations of persistent store and indexer. It is suggested that this set
> is kept unchanged:
> {{
> titan0 solr es
> ------------------------------------
> berkeley 0 1
> hbase 1 0
> cassandra 0 0
> }}
> With janusgraph (0.2.0) as the graph provider, Atlas *could* support
> additional combinations. Cassandra is included in this discussion pending
> response to ATLAS-2259.
> {{
> janus 0.2.0 solr es
> ------------------------------------
> berkeley ? 1
> hbase 1 ?
> cassandra ? ?
> }}
> It is suggested that the combinations marked with '1' should be continued and
> the remaining 4 combinations, marked with '?', should be considered. There
> seems to be evidence of people using all 4 of these combinations, although
> not necessarily with Atlas.
> Depending on the decision made above, we need to ensure that it is possible
> to build Atlas as a standalone package with any of the combinations - i.e.
> that they are mutually exclusive and do not interfere with one another. They
> currently interfere which makes it impossible to build Atlas with
> -Pdist,berkeley-elasticsearch because the 'dist' profile will exclude jars
> that are needed by the berkeley-elasticsearch profile - which leads to class
> not found exceptions when the Atlas server is started. The solution to this
> could be very simple, or slightly more sophisticated, depending on how many
> of the combinations we choose to support.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
