Re: R: critical question about oak: db connection
Hi Francesco, Your tests ran out of the box in my IDE (IntelliJ IDEA 15) using a local Postgres 9.3. Best regards, Manfred On 3/23/2016 8:27 AM, Ancona Francesco wrote: Hello, any news about question ? Thanks in advance, best regards -Messaggio originale- Da: Ancona Francesco [mailto:francesco.anc...@siav.it] Inviato: venerdì 18 marzo 2016 11:40 A: oak-dev@jackrabbit.apache.org Oggetto: R: critical question about oak: db connection Done. https://github.com/francescoancona/oaktest.git Thanks in advance, best regards -Messaggio originale- Da: Tomek Rekawek [mailto:reka...@adobe.com] Inviato: giovedì 17 marzo 2016 15:32 A: oak-dev@jackrabbit.apache.org Oggetto: Re: critical question about oak: db connection Hello Ancona, the mailing list didn’t allow to add an attachment. Could you post it somewhere online or (even better) put the code into github? Best regards, Tomek -- Tomek Rękawek | Adobe Research | www.adobe.com reka...@adobe.com On 17 Mar 2016, at 14:46, Ancona Francescowrote: Hello, i send you a maven project to connect with postgres. As i told you in other messages i know that oak test cases work; but they start always with RDBDocumentStore and use UpdateOp and other Oak methods to add nodes. Instead we'd like to use RDBDocumentNodeStore and we'd like to have jcrRepository and jcr methods to manage documents (nodes). I hope the project can be useful. Thanks in advance, best regards. -Messaggio originale- Da: Julian Reschke [mailto:julian.resc...@gmx.de] Inviato: mercoledì 16 marzo 2016 17:21 A: oak-dev@jackrabbit.apache.org Oggetto: Re: R: critical question about oak: db connection Ancona, you keep asking for more help but seem to ignore the feedback that you get. 1) oak-jcr and oak-run demonstrate that it is possible to run on RDBs; just run the tests. All the information that you need should be in the test cases. 2) Don't throw code snippets at us. Without complete classes we can try ourselves there is no way how we can find out what's wrong. So either start from the existing working code, or send self-contained test code we can compile and run ourselves. Best regards, Julian On 2016-03-16 16:28, Ancona Francesco wrote: Hi, Oak configuration with RDBMS doesn't work yet. I use the latest release 1.4.0 but i have the same problem In particular this is the code i use to initialize Oak final DocumentMK.Builder builder = new DocumentMK.Builder(); builder.setBlobStore(createFileSystemBlobStore()); final DocumentNodeStore ns = getRDBDocumentNodeStore(builder); // ds is datasource form postgres 9.4 DocumentStore documentStore = new RDBDocumentStore(ds, builder); builder.setDocumentStore(documentStore); DocumentNodeStore ns = new DocumentNodeStore(builder); DocumentNodeStore ns1 = new DocumentMK.Builder().setDocumentStore(documentStore).getNodeStore(); InitialContent ic = new InitialContent(); Oak oak = new Oak(ns1).with(ic); Jcr jcr = new Jcr(oak); Repository repo = jcr.createRepository(); and this is the stack trace: java.lang.IllegalStateException: This tree does not exist at org.apache.jackrabbit.oak.core.MutableTree.beforeWrite(MutableTree.java:353) at org.apache.jackrabbit.oak.core.MutableTree.setProperty(MutableTree.java:232) at org.apache.jackrabbit.oak.plugins.name.ReadWriteNamespaceRegistry.registerNamespace(ReadWriteNamespaceRegistry.java:92) at org.apache.jackrabbit.commons.cnd.TemplateBuilderFactory.setNamespace(TemplateBuilderFactory.java:92) at org.apache.jackrabbit.commons.cnd.CompactNodeTypeDefReader.doNameSpace(CompactNodeTypeDefReader.java:246) at org.apache.jackrabbit.commons.cnd.CompactNodeTypeDefReader.parse(CompactNodeTypeDefReader.java:200) at org.apache.jackrabbit.commons.cnd.CompactNodeTypeDefReader.(CompactNodeTypeDefReader.java:163) at org.apache.jackrabbit.commons.cnd.CompactNodeTypeDefReader.(CompactNodeTypeDefReader.java:139) at org.apache.jackrabbit.commons.cnd.CndImporter.registerNodeTypes(CndImporter.java:147) at org.apache.jackrabbit.oak.plugins.nodetype.write.NodeTypeRegistry.registerNodeTypes(NodeTypeRegistry.java:109) at org.apache.jackrabbit.oak.plugins.nodetype.write.NodeTypeRegistry.register(NodeTypeRegistry.java:104) at org.apache.jackrabbit.oak.plugins.nodetype.write.NodeTypeRegistry.registerBuiltIn(NodeTypeRegistry.java:86) at org.apache.jackrabbit.oak.plugins.nodetype.write.InitialContent.initialize(InitialContent.java:120) at org.apache.jackrabbit.oak.spi.lifecycle.CompositeInitializer.initialize(CompositeInitializer.java:48) at org.apache.jackrabbit.oak.spi.lifecycle.OakInitializer.initialize(OakInitializer.java:42) at org.apache.jackrabbit.oak.Oak.createNewContentRepository(Oak.java:628) at org.apache.jackrabbit.oak.Oak.createContentRepository(Oak.java:616) at
Re: [VOTE] Release Apache Jackrabbit Oak 1.2.13
[√] +1 Release this package as Apache Jackrabbit Oak 1.2.13 Davide
Re: [VOTE] Release Apache Jackrabbit Oak 1.2.13
[X] +1 Release this package as Apache Jackrabbit Oak 1.2.13 alex On Wed, Mar 23, 2016 at 3:34 PM, Davide Giannellawrote: > > A candidate for the Jackrabbit Oak 1.2.13 release is available at: > > https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.2.13/ > > The release candidate is a zip archive of the sources in: > > > https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.2.13/ > > The SHA1 checksum of the archive is > 0c4acf4c50656d5b36825a87ce6c66715e15b7d8. > > A staged Maven repository is available for review at: > > https://repository.apache.org/ > > The command for running automated checks against this release candidate is: > > $ sh check-release.sh oak 1.2.13 > 0c4acf4c50656d5b36825a87ce6c66715e15b7d8 > > Please vote on releasing this package as Apache Jackrabbit Oak 1.2.13. > The vote is open for the next 72 hours and passes if a majority of at > least three +1 Jackrabbit PMC votes are cast. > > [ ] +1 Release this package as Apache Jackrabbit Oak 1.2.13 > [ ] -1 Do not release this package because... > > Davide >
[VOTE] Release Apache Jackrabbit Oak 1.2.13
A candidate for the Jackrabbit Oak 1.2.13 release is available at: https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.2.13/ The release candidate is a zip archive of the sources in: https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.2.13/ The SHA1 checksum of the archive is 0c4acf4c50656d5b36825a87ce6c66715e15b7d8. A staged Maven repository is available for review at: https://repository.apache.org/ The command for running automated checks against this release candidate is: $ sh check-release.sh oak 1.2.13 0c4acf4c50656d5b36825a87ce6c66715e15b7d8 Please vote on releasing this package as Apache Jackrabbit Oak 1.2.13. The vote is open for the next 72 hours and passes if a majority of at least three +1 Jackrabbit PMC votes are cast. [ ] +1 Release this package as Apache Jackrabbit Oak 1.2.13 [ ] -1 Do not release this package because... Davide
Re: parent pom env.OAK_INTEGRATION_TESTING
On 23/03/2016 11:18, Jukka Zitting wrote: > See https://issues.apache.org/jira/browse/OAK-163 for original discussion > about the environment flag. > > Back then the integration tests were only just becoming too long to run as > a part of the regular build, so it made sense to keep that option around > for people who wanted the earlier behavior. But I'd be surprised if someone > still uses the flag. > > Thanks Jukka. Nice to see you again ;) Speaking of CI, none of the CIs we currently have in place that I'm aware are using such flag. It feels safe therefore to change it. Last call: any objections? :) Davide
Re: parent pom env.OAK_INTEGRATION_TESTING
See https://issues.apache.org/jira/browse/OAK-163 for original discussion about the environment flag. Back then the integration tests were only just becoming too long to run as a part of the regular build, so it made sense to keep that option around for people who wanted the earlier behavior. But I'd be surprised if someone still uses the flag. Best, Jukka On Wed, Mar 23, 2016 at 5:03 AM Davide Giannellawrote: > On 23/03/2016 03:11, Chetan Mehrotra wrote: > > On Tue, Mar 22, 2016 at 9:49 PM, Davide Giannella > wrote: > >> I can't really recall why and if we use this. > > Its referred to in main README.md so as to allow a developer to always > > enable running of integration test > > > Thanks Chetan. > > Is anyone using this, or aware of any process using this? > > Objections if I replace it with something else? > > Thanks > Davide >
OAK +Remote SOLR OOTB integration queries
Hi All, As in here http://jackrabbit.apache.org/oak/docs/query/solr.html Trying use remote SOLR with OAKa Need to know if these are supported 1) How to control Indexing child nodes of jcr:content , ex:- controlling the depth via some configuration 2) options to merge the child nodes into 1 single document in solr 3) how to apply SOLR index inclusion & exclusion rules Please share if any such configuration exists or ideas with regardsSri
Re: parent pom env.OAK_INTEGRATION_TESTING
On 23/03/2016 03:11, Chetan Mehrotra wrote: > On Tue, Mar 22, 2016 at 9:49 PM, Davide Giannellawrote: >> I can't really recall why and if we use this. > Its referred to in main README.md so as to allow a developer to always > enable running of integration test > Thanks Chetan. Is anyone using this, or aware of any process using this? Objections if I replace it with something else? Thanks Davide
R: critical question about oak: db connection
Hello, any news about question ? Thanks in advance, best regards -Messaggio originale- Da: Ancona Francesco [mailto:francesco.anc...@siav.it] Inviato: venerdì 18 marzo 2016 11:40 A: oak-dev@jackrabbit.apache.org Oggetto: R: critical question about oak: db connection Done. https://github.com/francescoancona/oaktest.git Thanks in advance, best regards -Messaggio originale- Da: Tomek Rekawek [mailto:reka...@adobe.com] Inviato: giovedì 17 marzo 2016 15:32 A: oak-dev@jackrabbit.apache.org Oggetto: Re: critical question about oak: db connection Hello Ancona, the mailing list didn’t allow to add an attachment. Could you post it somewhere online or (even better) put the code into github? Best regards, Tomek -- Tomek Rękawek | Adobe Research | www.adobe.com reka...@adobe.com > On 17 Mar 2016, at 14:46, Ancona Francescowrote: > > Hello, > i send you a maven project to connect with postgres. > > As i told you in other messages i know that oak test cases work; but they > start always with RDBDocumentStore and use UpdateOp and other Oak methods to > add nodes. > > Instead we'd like to use RDBDocumentNodeStore and we'd like to have > jcrRepository and jcr methods to manage documents (nodes). > > I hope the project can be useful. > > Thanks in advance, > best regards. > > -Messaggio originale- > Da: Julian Reschke [mailto:julian.resc...@gmx.de] > Inviato: mercoledì 16 marzo 2016 17:21 > A: oak-dev@jackrabbit.apache.org > Oggetto: Re: R: critical question about oak: db connection > > Ancona, > > you keep asking for more help but seem to ignore the feedback that you get. > > 1) oak-jcr and oak-run demonstrate that it is possible to run on RDBs; just > run the tests. All the information that you need should be in the test cases. > > 2) Don't throw code snippets at us. Without complete classes we can try > ourselves there is no way how we can find out what's wrong. > > So either start from the existing working code, or send self-contained test > code we can compile and run ourselves. > > Best regards, Julian > > > On 2016-03-16 16:28, Ancona Francesco wrote: >> Hi, >> Oak configuration with RDBMS doesn't work yet. >> >> I use the latest release 1.4.0 but i have the same problem >> >> In particular this is the code i use to initialize Oak >> >> final DocumentMK.Builder builder = new DocumentMK.Builder(); >> builder.setBlobStore(createFileSystemBlobStore()); >> final DocumentNodeStore ns = >> getRDBDocumentNodeStore(builder); >> >> // ds is datasource form postgres 9.4 DocumentStore documentStore = >> new RDBDocumentStore(ds, builder); >> builder.setDocumentStore(documentStore); >> DocumentNodeStore ns = new DocumentNodeStore(builder); >> DocumentNodeStore ns1 = new >> DocumentMK.Builder().setDocumentStore(documentStore).getNodeStore(); >> InitialContent ic = new InitialContent(); >> Oak oak = new Oak(ns1).with(ic); >> Jcr jcr = new Jcr(oak); >> Repository repo = jcr.createRepository(); >> >> >> and this is the stack trace: >> java.lang.IllegalStateException: This tree does not exist >> at >> org.apache.jackrabbit.oak.core.MutableTree.beforeWrite(MutableTree.java:353) >> at >> org.apache.jackrabbit.oak.core.MutableTree.setProperty(MutableTree.java:232) >> at >> org.apache.jackrabbit.oak.plugins.name.ReadWriteNamespaceRegistry.registerNamespace(ReadWriteNamespaceRegistry.java:92) >> at >> org.apache.jackrabbit.commons.cnd.TemplateBuilderFactory.setNamespace(TemplateBuilderFactory.java:92) >> at >> org.apache.jackrabbit.commons.cnd.CompactNodeTypeDefReader.doNameSpace(CompactNodeTypeDefReader.java:246) >> at >> org.apache.jackrabbit.commons.cnd.CompactNodeTypeDefReader.parse(CompactNodeTypeDefReader.java:200) >> at >> org.apache.jackrabbit.commons.cnd.CompactNodeTypeDefReader.(CompactNodeTypeDefReader.java:163) >> at >> org.apache.jackrabbit.commons.cnd.CompactNodeTypeDefReader.(CompactNodeTypeDefReader.java:139) >> at >> org.apache.jackrabbit.commons.cnd.CndImporter.registerNodeTypes(CndImporter.java:147) >> at >> org.apache.jackrabbit.oak.plugins.nodetype.write.NodeTypeRegistry.registerNodeTypes(NodeTypeRegistry.java:109) >> at >> org.apache.jackrabbit.oak.plugins.nodetype.write.NodeTypeRegistry.register(NodeTypeRegistry.java:104) >> at >> org.apache.jackrabbit.oak.plugins.nodetype.write.NodeTypeRegistry.registerBuiltIn(NodeTypeRegistry.java:86) >> at >> org.apache.jackrabbit.oak.plugins.nodetype.write.InitialContent.initialize(InitialContent.java:120) >> at >> org.apache.jackrabbit.oak.spi.lifecycle.CompositeInitializer.initialize(CompositeInitializer.java:48) >> at >> org.apache.jackrabbit.oak.spi.lifecycle.OakInitializer.initialize(OakInitializer.java:42) >> at org.apache.jackrabbit.oak.Oak.createNewContentRepository(Oak.java:628) >> at