No problem to move to jdk 7. Regards Eri -----Message d'origine----- De : Olivier Lamy [mailto:[email protected]] Envoyé : mardi 1 avril 2014 03:05 À : [email protected] Objet : Re: Cassandra storage and jdk version?
On 1 April 2014 11:57, Brett Porter <[email protected]> wrote: > > On 1 Apr 2014, at 11:37 am, Olivier Lamy <[email protected]> wrote: > >> Hi Folks, >> >> I finished the implementation of the metadata storage using Cassandra. >> See docs here: >> http://archiva.apache.org/docs/2.0.2-SNAPSHOT/adminguide/repositories >> -content-storage.html >> Builds available from here: >> https://builds.apache.org/view/A-D/view/Archiva/job/archiva-all-maven >> -3.1.x-jdk-1.7/ > > Will take a look! > > What is the impact on the app overall in terms of deployment, performance, memory, etc.? Less memory usage :-) as we do not run anymore internally the Jackrabbit stack. Deployment is just a matter of configuring 2 files. Having that dynamic need huge/complicated refactoring! I need to investigate a bit to improve a bit performance. (some stuff can be done with simply using cql queries) but that's not too bad :-) An idea I have in mind is to propose an alternate file storage in Cassandra to have a real scalable architecture (local storage could act as cache especially for released artifacts) > >> >> The question is now the jdk version. With this cassandra runtime >> version it's now 1.7. >> So are we ok to set 1.7 as a prerequisite? > > No problem here. I was just started a discussion here and will probably start a more official vote soon. > > - Brett > > -- > Brett Porter @brettporter > http://brettporter.wordpress.com/ > http://au.linkedin.com/in/brettporter > -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy
