Re: New JIRA Components

2017-03-26 Thread Chetan Mehrotra
Created new jira component now query - 55 issues https://issues.apache.org/jira/browse/OAK/component/12320003 indexing - 18 issues https://issues.apache.org/jira/browse/OAK/component/12332439 property-index - 18 issues https://issues.apache.org/jira/browse/OAK/component/12332440 Chetan Mehrotra

Re: New JIRA Components

2017-03-26 Thread Chetan Mehrotra
On Fri, Mar 24, 2017 at 7:36 PM, Thomas Mueller wrote: > * Sometimes there is an overlap, in which case I guess multiple components > needs to be set. yes > * What to do with old issue. For now no need to modify old resolved issues. This is only applicable for current open

Re: New JIRA Components

2017-03-23 Thread Chetan Mehrotra
On Thu, Mar 23, 2017 at 7:27 PM, Davide Giannella wrote: > otherwise I would expect to have > property-index, lucene-index, solr-index or whatever will come (if) in We already have 'lucene' and 'solr' component for them. 'indexing' is referring to logic mostly present in

Re: New JIRA Components

2017-03-23 Thread Davide Giannella
On 23/03/2017 09:11, Chetan Mehrotra wrote: > 1. query - For any issue related to QueryEngine +1 > 2. indexing - For any issue related to sync or async indexing > 3. property-index - For any issue in Property index implementation I'd say we stick only with `indexing`; otherwise I would expect

New JIRA Components

2017-03-23 Thread Chetan Mehrotra
Currently any change done in indexing, property index, query engine area done in oak-core is logged against "query" component. Given these are bit different I propose to split the component in following way 1. query - For any issue related to QueryEngine 2. indexing - For any issue related to