james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tellier Benoit (JIRA)" <server-...@james.apache.org>
Subject [jira] [Updated] (JAMES-1588) Create a project to centralize Cassandra tools
Date Fri, 17 Jul 2015 14:56:04 GMT

     [ https://issues.apache.org/jira/browse/JAMES-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tellier Benoit updated JAMES-1588:
----------------------------------
    Description: 
As we are starting to develop data tools based on Cassandra, we realized we would use tools
we defined for the Cassandra mailbox. But :

 - We don't want a dependency to the cassandra mailbox in our data-cassandra module
 - We do not want to duplicate information.

Hence we prefer introducing a new module, that centralize tools needed by modules relying
on Cassandra ( for now the Cassandra mailbox, and the data-cassandra module, Cassandra MPT
module ).

As we think this can be a common need to several backend implementation, we want to create
a dedicated project for centralizing back-end tools, that will be calles james-backends. Each
back-end ( eg : cassandra, jpa, hbase, etc ... ) will create its submodule in it and will
use it in other places (MPT, Mailbox, james (server) ).

Let us now if you have any feedback on this proposal.

  was:
As we are starting to develop data tools based on Cassandra, we realized we would use tools
we defined for the Cassandra mailbox. But :

 - We don't want a depandancy to the cassandra mailbox in our data-cassandra module ( and
the reciproque )
 - We do not want to duplicate information.

Hence we prefer introducing a new module, that centralize tools needed by modules relying
on Cassandra ( for now the Cassandra mailbox, and the data-cassandra module ).

As we think this can be a common need to several backend implementation, we want to create
a folder dedicated to these back-end centralization projects :

james
          /app
                 ...
          /backend
                 /cassandra
                 ...
          /container
                 ...

Let us now if you have any feedback on this proposal.


> Create a project to centralize Cassandra tools
> ----------------------------------------------
>
>                 Key: JAMES-1588
>                 URL: https://issues.apache.org/jira/browse/JAMES-1588
>             Project: James Server
>          Issue Type: Improvement
>            Reporter: Tellier Benoit
>
> As we are starting to develop data tools based on Cassandra, we realized we would use
tools we defined for the Cassandra mailbox. But :
>  - We don't want a dependency to the cassandra mailbox in our data-cassandra module
>  - We do not want to duplicate information.
> Hence we prefer introducing a new module, that centralize tools needed by modules relying
on Cassandra ( for now the Cassandra mailbox, and the data-cassandra module, Cassandra MPT
module ).
> As we think this can be a common need to several backend implementation, we want to create
a dedicated project for centralizing back-end tools, that will be calles james-backends. Each
back-end ( eg : cassandra, jpa, hbase, etc ... ) will create its submodule in it and will
use it in other places (MPT, Mailbox, james (server) ).
> Let us now if you have any feedback on this proposal.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message