Backport of OAK-4933 to 1.6

Hi, I would like to backport OAK-4933 to 1.6. The impact should be minimal since the changes are about bringing the AzureBlobStore connector to 1.6. Changes are: - new module - changes in oak-run to support the azure data store Thanks, Raul

Re: New JIRA component for observation

On Mon, Mar 27, 2017 at 12:56 PM, Marcel Reutegger wrote: > In my view this indicates that the existing modules should probably be split > and we'd be back to a 1:1 relation between modules in SVN and components in > JIRA. Alternatively, we could also use JIRA labels and group

Re: New JIRA component for observation

On 27.03.17 09:26, Marcel Reutegger wrote: I'm wondering if this is the best approach. Initially we used the JIRA component 1:1 for modules we have in SVN. Now we also use them for sub-modules like 'documentmk', 'mongomk', 'property-index', ... +1 Michael

Re: New JIRA component for observation

Hi, I'm wondering if this is the best approach. Initially we used the JIRA component 1:1 for modules we have in SVN. Now we also use them for sub-modules like 'documentmk', 'mongomk', 'property-index', ... In my view this indicates that the existing modules should probably be split and we'd

R: problem on oak jcr sql2 query

Sorry. We are using Oak 1.4.10 and solr 4.10.4 i send you also a pdf example: the searched word is "sezione" In another document ([nt:file] that doesn't have childs) i'd want match only through metadata that contains the word "company" Actually i resolved the problem executing a query like

Re: Logger category org.apache.jackrabbit.oak.jcr.operations.writes includes 'refresh' operation

Its a write operation as it has potential to change the session state. If the refresh is done with keepChanges=false the current transient changes would be discarded. Chetan Mehrotra On Fri, Mar 24, 2017 at 2:07 PM, Robert Munteanu wrote: > Hi, > > With Oak 1.6.1 I've