[jira] [Comment Edited] (OAK-8166) Index definition with orderable property definitions with and without functions breaks index

[ https://issues.apache.org/jira/browse/OAK-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16807614#comment-16807614 ] Nitin Gupta edited comment on OAK-8166 at 4/2/19 10:00 AM: --- While writing a test

[jira] [Commented] (OAK-8166) Index definition with orderable property definitions with and without functions breaks index

[ https://issues.apache.org/jira/browse/OAK-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16807614#comment-16807614 ] Nitin Gupta commented on OAK-8166: -- While writing a test to reproduce this - realized that this only

[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

[ https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8177: - Attachment: OAK-8177_3.patch > Add logging around getReferenceCheckpoint method >

[jira] [Commented] (OAK-8177) Add logging around getReferenceCheckpoint method

[ https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16807763#comment-16807763 ] Nitin Gupta commented on OAK-8177: -- [~tmueller] - {code:java} I think the first "log.info("Getting

[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

[ https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8177: - Attachment: (was: OAK-8177_3.patch) > Add logging around getReferenceCheckpoint method >

[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

[ https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8177: - Attachment: OAK-8177_3.patch > Add logging around getReferenceCheckpoint method >

[jira] [Commented] (OAK-8177) Add logging around getReferenceCheckpoint method

[ https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16807892#comment-16807892 ] Nitin Gupta commented on OAK-8177: -- [~tmueller] - sorry for the to and fro on a trivial change . I have

[jira] [Commented] (OAK-8166) Index definition with orderable property definitions with and without functions breaks index

[ https://issues.apache.org/jira/browse/OAK-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806380#comment-16806380 ] Nitin Gupta commented on OAK-8166: -- Starting work on this issue . > Index definition with orderable

[jira] [Updated] (OAK-8166) Index definition with orderable property definitions with and without functions breaks index

[ https://issues.apache.org/jira/browse/OAK-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8166: - Attachment: OAK-8166_1.patch > Index definition with orderable property definitions with and without >

[jira] [Commented] (OAK-8166) Index definition with orderable property definitions with and without functions breaks index

[ https://issues.apache.org/jira/browse/OAK-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808612#comment-16808612 ] Nitin Gupta commented on OAK-8166: -- The problem here is that - Since we have 2 property definitions in

[jira] [Comment Edited] (OAK-8138) In cases where search hit count is less than sample size defined for statistical mode for facets, secure mode should be used so that the counts are accurate for non-

[ https://issues.apache.org/jira/browse/OAK-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16800386#comment-16800386 ] Nitin Gupta edited comment on OAK-8138 at 3/25/19 3:57 AM: --- [~tmueller] ,

[jira] [Commented] (OAK-8138) In cases where search hit count is less than sample size defined for statistical mode for facets, secure mode should be used so that the counts are accurate for non-admin

[ https://issues.apache.org/jira/browse/OAK-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16800386#comment-16800386 ] Nitin Gupta commented on OAK-8138: -- [~tmueller] , [~catholicon] - here's the updated patch -

[jira] [Updated] (OAK-8138) In cases where search hit count is less than sample size defined for statistical mode for facets, secure mode should be used so that the counts are accurate for non-admin u

[ https://issues.apache.org/jira/browse/OAK-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8138: - Attachment: OAK-8138_1.patch > In cases where search hit count is less than sample size defined for >

[jira] [Commented] (OAK-8166) Index definition with orderable property definitions with and without functions breaks index

[ https://issues.apache.org/jira/browse/OAK-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16809577#comment-16809577 ] Nitin Gupta commented on OAK-8166: -- [~catholicon] - yup -this does sounds better - I was mostly concerned

[jira] [Comment Edited] (OAK-8166) Index definition with orderable property definitions with and without functions breaks index

[ https://issues.apache.org/jira/browse/OAK-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808720#comment-16808720 ] Nitin Gupta edited comment on OAK-8166 at 4/3/19 1:28 PM: -- [~tmueller] ,

[jira] [Comment Edited] (OAK-8166) Index definition with orderable property definitions with and without functions breaks index

[ https://issues.apache.org/jira/browse/OAK-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808720#comment-16808720 ] Nitin Gupta edited comment on OAK-8166 at 4/3/19 1:29 PM: -- [~tmueller] ,

[jira] [Comment Edited] (OAK-8166) Index definition with orderable property definitions with and without functions breaks index

[ https://issues.apache.org/jira/browse/OAK-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808720#comment-16808720 ] Nitin Gupta edited comment on OAK-8166 at 4/3/19 1:30 PM: -- [~tmueller] ,

[jira] [Commented] (OAK-8166) Index definition with orderable property definitions with and without functions breaks index

[ https://issues.apache.org/jira/browse/OAK-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808739#comment-16808739 ] Nitin Gupta commented on OAK-8166: -- [~catholicon] - that was my first thought of the fix - to fix it in

[jira] [Commented] (OAK-8166) Index definition with orderable property definitions with and without functions breaks index

[ https://issues.apache.org/jira/browse/OAK-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808720#comment-16808720 ] Nitin Gupta commented on OAK-8166: -- [~tmueller] , [~catholicon] - the field names are not colliding here .

[jira] [Commented] (OAK-8138) In cases where search hit count is less than sample size defined for statistical mode for facets, secure mode should be used so that the counts are accurate for non-admin

[ https://issues.apache.org/jira/browse/OAK-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803778#comment-16803778 ] Nitin Gupta commented on OAK-8138: -- [~tmueller] - [^OAK-8138_1.patch] - this is the final patch for this .

[jira] [Created] (OAK-8177) Add logging around getReferenceCheckpoint method

Nitin Gupta created OAK-8177: Summary: Add logging around getReferenceCheckpoint method Key: OAK-8177 URL: https://issues.apache.org/jira/browse/OAK-8177 Project: Jackrabbit Oak Issue Type:

[jira] [Commented] (OAK-8177) Add logging around getReferenceCheckpoint method

[ https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804710#comment-16804710 ] Nitin Gupta commented on OAK-8177: -- [~tmueller] - here's a patch for this - [^OAK-8177_1.patch] . Can you

[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

[ https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8177: - Attachment: OAK-8177_2.patch > Add logging around getReferenceCheckpoint method >

[jira] [Issue Comment Deleted] (OAK-8177) Add logging around getReferenceCheckpoint method

[ https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8177: - Comment: was deleted (was: [~tmueller] - thanks - here's the changed patch - [^OAK-8177_2.patch]) > Add

[jira] [Commented] (OAK-8177) Add logging around getReferenceCheckpoint method

[ https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804753#comment-16804753 ] Nitin Gupta commented on OAK-8177: -- [~tmueller] - thanks - here's the changed patch - [^OAK-8177_2.patch]

[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

[ https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8177: - Attachment: (was: OAK-8177_2.patch) > Add logging around getReferenceCheckpoint method >

[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

[ https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8177: - Attachment: OAK-8177_1.patch > Add logging around getReferenceCheckpoint method >

[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

[ https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8177: - Attachment: OAK-8177_2.patch > Add logging around getReferenceCheckpoint method >

[jira] [Commented] (OAK-8177) Add logging around getReferenceCheckpoint method

[ https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804758#comment-16804758 ] Nitin Gupta commented on OAK-8177: -- [~tmueller] thanks ..here's the updated patch - [^OAK-8177_2.patch] >

[jira] [Commented] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771822#comment-16771822 ] Nitin Gupta commented on OAK-8035: -- [~reschke] - Just find it a bit more fluent with assertions - makes

[jira] [Comment Edited] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771857#comment-16771857 ] Nitin Gupta edited comment on OAK-8035 at 2/19/19 12:03 PM: [~reschke] - agreed

[jira] [Comment Edited] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771857#comment-16771857 ] Nitin Gupta edited comment on OAK-8035 at 2/19/19 11:59 AM: [~reschke] - agreed

[jira] [Updated] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8035: - Attachment: OAK-8035_4.patch > Debug logging when two or more indices have same or very close cost amounts

[jira] [Commented] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771857#comment-16771857 ] Nitin Gupta commented on OAK-8035: -- [~reschke] - agreed .  I was just about to add this patch here 

[jira] [Created] (OAK-8138) In cases where search hit count is less than sample size defined for statistical mode for facets, secure mode should be used so that the counts are accurate for non-admin u

Nitin Gupta created OAK-8138: Summary: In cases where search hit count is less than sample size defined for statistical mode for facets, secure mode should be used so that the counts are accurate for non-admin users. Key: OAK-8138

[jira] [Commented] (OAK-8114) IndexDefinitionBuilder should be smarter when to reindex while updating a definition

[ https://issues.apache.org/jira/browse/OAK-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16790282#comment-16790282 ] Nitin Gupta commented on OAK-8114: -- [^OAK-8114_2.patch] - Added test cases for remaining use cases and

[jira] [Updated] (OAK-8114) IndexDefinitionBuilder should be smarter when to reindex while updating a definition

[ https://issues.apache.org/jira/browse/OAK-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8114: - Attachment: OAK-8114_2.patch > IndexDefinitionBuilder should be smarter when to reindex while updating a

[jira] [Commented] (OAK-8114) IndexDefinitionBuilder should be smarter when to reindex while updating a definition

[ https://issues.apache.org/jira/browse/OAK-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16790165#comment-16790165 ] Nitin Gupta commented on OAK-8114: -- Need to handle for these scenarios as well (These shouldn't req

[jira] [Updated] (OAK-8114) IndexDefinitionBuilder should be smarter when to reindex while updating a definition

[ https://issues.apache.org/jira/browse/OAK-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8114: - Attachment: OAK-8114_1.patch > IndexDefinitionBuilder should be smarter when to reindex while updating a

[jira] [Commented] (OAK-8114) IndexDefinitionBuilder should be smarter when to reindex while updating a definition

[ https://issues.apache.org/jira/browse/OAK-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789162#comment-16789162 ] Nitin Gupta commented on OAK-8114: -- So In effect -   as of now - I could find these 3 properties whose

[jira] [Comment Edited] (OAK-8114) IndexDefinitionBuilder should be smarter when to reindex while updating a definition

[ https://issues.apache.org/jira/browse/OAK-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789158#comment-16789158 ] Nitin Gupta edited comment on OAK-8114 at 3/11/19 6:05 AM: --- * Properties on

[jira] [Commented] (OAK-8114) IndexDefinitionBuilder should be smarter when to reindex while updating a definition

[ https://issues.apache.org/jira/browse/OAK-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789158#comment-16789158 ] Nitin Gupta commented on OAK-8114: -- * Properties on Property node*   - name (string) // Any change

[jira] [Comment Edited] (OAK-8114) IndexDefinitionBuilder should be smarter when to reindex while updating a definition

[ https://issues.apache.org/jira/browse/OAK-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789162#comment-16789162 ] Nitin Gupta edited comment on OAK-8114 at 3/11/19 6:10 AM: --- So In effect -   as

[jira] [Commented] (OAK-8114) IndexDefinitionBuilder should be smarter when to reindex while updating a definition

[ https://issues.apache.org/jira/browse/OAK-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791565#comment-16791565 ] Nitin Gupta commented on OAK-8114: -- PR for this change -

[jira] [Commented] (OAK-8138) In cases where search hit count is less than sample size defined for statistical mode for facets, secure mode should be used so that the counts are accurate for non-admin

[ https://issues.apache.org/jira/browse/OAK-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16796827#comment-16796827 ] Nitin Gupta commented on OAK-8138: -- Got some review comments from Vikas on

[jira] [Comment Edited] (OAK-8138) In cases where search hit count is less than sample size defined for statistical mode for facets, secure mode should be used so that the counts are accurate for non-

[ https://issues.apache.org/jira/browse/OAK-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16796827#comment-16796827 ] Nitin Gupta edited comment on OAK-8138 at 3/20/19 5:58 AM: --- Got some review

[jira] [Comment Edited] (OAK-8138) In cases where search hit count is less than sample size defined for statistical mode for facets, secure mode should be used so that the counts are accurate for non-

[ https://issues.apache.org/jira/browse/OAK-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16796827#comment-16796827 ] Nitin Gupta edited comment on OAK-8138 at 3/20/19 5:58 AM: --- Got some review

[jira] [Commented] (OAK-8114) IndexDefinitionBuilder should be smarter when to reindex while updating a definition

[ https://issues.apache.org/jira/browse/OAK-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16790462#comment-16790462 ] Nitin Gupta commented on OAK-8114: -- [~tmueller] - thanks  I had figured out the cost overrides

[jira] [Assigned] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta reassigned OAK-8035: Assignee: Nitin Gupta > Debug logging when two or more indices have same or very close cost amounts

[jira] [Created] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

Nitin Gupta created OAK-8035: Summary: Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index Key: OAK-8035 URL:

[jira] [Updated] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8035: - Description: Steps to reproduce - # You would need two index definitions of same query index type , let's

[jira] [Updated] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8035: - Attachment: OAK-8035_2.patch > Debug logging when two or more indices have same or very close cost amounts

[jira] [Commented] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16765981#comment-16765981 ] Nitin Gupta commented on OAK-8035: -- [~tmueller] - updated patch - [^OAK-8035_2.patch]  as per your

[jira] [Comment Edited] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767015#comment-16767015 ] Nitin Gupta edited comment on OAK-8035 at 2/13/19 10:09 AM: [~tmueller] - yup - 

[jira] [Commented] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767015#comment-16767015 ] Nitin Gupta commented on OAK-8035: -- [~tmueller] - yup -  I don't have commit rights . This is actually my

[jira] [Updated] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8035: - Attachment: OAK-8035.patch > Debug logging when two or more indices have same or very close cost amounts

[jira] [Commented] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16764746#comment-16764746 ] Nitin Gupta commented on OAK-8035: -- [~teofili] - I have attached a patch for this - [^OAK-8035.patch] .

[jira] [Updated] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8035: - Attachment: OAK-8035_3.patch > Debug logging when two or more indices have same or very close cost amounts

[jira] [Commented] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769518#comment-16769518 ] Nitin Gupta commented on OAK-8035: -- [~reschke] - thanks for pointing out the problem and sorry for the

[jira] [Resolved] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta resolved OAK-8035. -- Resolution: Fixed Fix Version/s: 1.11.0 > Debug logging when two or more indices have same or

[jira] [Commented] (OAK-8035) Debug logging when two or more indices have same or very close cost amounts doesn't work in case both indices belong to the same type of Query Index

[ https://issues.apache.org/jira/browse/OAK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769628#comment-16769628 ] Nitin Gupta commented on OAK-8035: -- [~reschke] - thanks > Debug logging when two or more indices have

[jira] [Commented] (OAK-8114) IndexDefinitionBuilder should be smarter when to reindex while updating a definition

[ https://issues.apache.org/jira/browse/OAK-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793630#comment-16793630 ] Nitin Gupta commented on OAK-8114: -- [~tmueller] - here -

[jira] [Created] (OAK-8328) Bug in index definition can block indexing / cause indexing in a loop

Nitin Gupta created OAK-8328: Summary: Bug in index definition can block indexing / cause indexing in a loop Key: OAK-8328 URL: https://issues.apache.org/jira/browse/OAK-8328 Project: Jackrabbit Oak

[jira] [Commented] (OAK-8344) Expose local index directory size as a metric

[ https://issues.apache.org/jira/browse/OAK-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849783#comment-16849783 ] Nitin Gupta commented on OAK-8344: -- [~tmueller] - added the line breaks here - [^OAK-8344_1.patch] >

[jira] [Updated] (OAK-8344) Expose local index directory size as a metric

[ https://issues.apache.org/jira/browse/OAK-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8344: - Attachment: OAK-8344_1.patch > Expose local index directory size as a metric >

[jira] [Updated] (OAK-8344) Expose local index directory size as a metric

[ https://issues.apache.org/jira/browse/OAK-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8344: - Attachment: OAK-8344.patch > Expose local index directory size as a metric >

[jira] [Commented] (OAK-8344) Expose local index directory size as a metric

[ https://issues.apache.org/jira/browse/OAK-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848738#comment-16848738 ] Nitin Gupta commented on OAK-8344: -- Patch available for review - [^OAK-8344.patch] [~tmueller] ,

[jira] [Commented] (OAK-8328) Bug in index definition can block indexing / cause indexing in a loop

[ https://issues.apache.org/jira/browse/OAK-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862900#comment-16862900 ] Nitin Gupta commented on OAK-8328: -- [~tmueller] - updated patch here - [^OAK-8328_2.patch] . This fixes

[jira] [Updated] (OAK-8328) Bug in index definition can block indexing / cause indexing in a loop

[ https://issues.apache.org/jira/browse/OAK-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8328: - Attachment: OAK-8328_2.patch > Bug in index definition can block indexing / cause indexing in a loop >

[jira] [Commented] (OAK-8328) Bug in index definition can block indexing / cause indexing in a loop

[ https://issues.apache.org/jira/browse/OAK-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864294#comment-16864294 ] Nitin Gupta commented on OAK-8328: -- [~tmueller] > The added "try \{ ... } catch" requires adding spaces

[jira] [Commented] (OAK-8328) Bug in index definition can block indexing / cause indexing in a loop

[ https://issues.apache.org/jira/browse/OAK-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860969#comment-16860969 ] Nitin Gupta commented on OAK-8328: -- Sure [~tmueller] - I will provide a test case too . > Bug in index

[jira] [Commented] (OAK-8328) Bug in index definition can block indexing / cause indexing in a loop

[ https://issues.apache.org/jira/browse/OAK-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861030#comment-16861030 ] Nitin Gupta commented on OAK-8328: -- Update - There is a test case in oak-core failing with this patch .

[jira] [Updated] (OAK-8328) Bug in index definition can block indexing / cause indexing in a loop

[ https://issues.apache.org/jira/browse/OAK-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8328: - Attachment: OAK-8328.patch > Bug in index definition can block indexing / cause indexing in a loop >

[jira] [Commented] (OAK-8328) Bug in index definition can block indexing / cause indexing in a loop

[ https://issues.apache.org/jira/browse/OAK-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845767#comment-16845767 ] Nitin Gupta commented on OAK-8328: -- [~tmueller] - Patch here - [^OAK-8328.patch] . This has changes as per

[jira] [Commented] (OAK-8328) Bug in index definition can block indexing / cause indexing in a loop

[ https://issues.apache.org/jira/browse/OAK-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847315#comment-16847315 ] Nitin Gupta commented on OAK-8328: -- Thanks [~tmueller] . > Bug in index definition can block indexing /

[jira] [Created] (OAK-8344) Expose local index directory size as a metric

Nitin Gupta created OAK-8344: Summary: Expose local index directory size as a metric Key: OAK-8344 URL: https://issues.apache.org/jira/browse/OAK-8344 Project: Jackrabbit Oak Issue Type: Task

[jira] [Updated] (OAK-8344) Expose local index directory size as a metric

[ https://issues.apache.org/jira/browse/OAK-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8344: - Component/s: indexing > Expose local index directory size as a metric >

[jira] [Updated] (OAK-8344) Expose local index directory size as a metric

[ https://issues.apache.org/jira/browse/OAK-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8344: - Component/s: lucene > Expose local index directory size as a metric >

[jira] [Commented] (OAK-8328) Bug in index definition can block indexing / cause indexing in a loop

[ https://issues.apache.org/jira/browse/OAK-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16843958#comment-16843958 ] Nitin Gupta commented on OAK-8328: -- [~tmueller] - A PR here -

[jira] [Updated] (OAK-8166) Index definition with orderable property definitions with and without functions breaks index

[ https://issues.apache.org/jira/browse/OAK-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8166: - Attachment: OAK-8166_2.patch > Index definition with orderable property definitions with and without >

[jira] [Commented] (OAK-8166) Index definition with orderable property definitions with and without functions breaks index

[ https://issues.apache.org/jira/browse/OAK-8166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830326#comment-16830326 ] Nitin Gupta commented on OAK-8166: -- [~catholicon] - Sorry this fell out of the radar due to other issues -

[jira] [Created] (OAK-8455) Memory Node store implementation of ProeprtyState throws Exception that is not in line with the API documentation

Nitin Gupta created OAK-8455: Summary: Memory Node store implementation of ProeprtyState throws Exception that is not in line with the API documentation Key: OAK-8455 URL:

[jira] [Updated] (OAK-8455) Memory Node store implementation of ProeprtyState throws Exception that is not in line with the API documentation

[ https://issues.apache.org/jira/browse/OAK-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8455: - Description: As per the api doc here

[jira] [Updated] (OAK-8455) Memory Node store implementation of PropertyState throws Exception that is not in line with the API documentation

[ https://issues.apache.org/jira/browse/OAK-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8455: - Summary: Memory Node store implementation of PropertyState throws Exception that is not in line with the

[jira] [Updated] (OAK-8455) Memory Node store implementation of PropertyState throws Exception that is not in line with the API documentation

[ https://issues.apache.org/jira/browse/OAK-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta updated OAK-8455: - Component/s: store-spi > Memory Node store implementation of PropertyState throws Exception that is > not

[jira] [Commented] (OAK-8328) Bug in index definition can block indexing / cause indexing in a loop

[ https://issues.apache.org/jira/browse/OAK-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877459#comment-16877459 ] Nitin Gupta commented on OAK-8328: -- [~tmueller] - I created a bug describing the difference in

[jira] [Commented] (OAK-8328) Bug in index definition can block indexing / cause indexing in a loop

[ https://issues.apache.org/jira/browse/OAK-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880001#comment-16880001 ] Nitin Gupta commented on OAK-8328: -- [~tmueller] - I have added the missing test case that was blocked on

[jira] [Commented] (OAK-8455) Memory Node store implementation of PropertyState throws Exception that is not in line with the API documentation

[ https://issues.apache.org/jira/browse/OAK-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1688#comment-1688 ] Nitin Gupta commented on OAK-8455: -- [~tmueller] - I have a patch here - [^OAK-8455_1.patch] . Ran all the

[jira] [Closed] (OAK-8526) IndexDefinitionBuilder should support setting up index tags

[ https://issues.apache.org/jira/browse/OAK-8526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta closed OAK-8526. > IndexDefinitionBuilder should support setting up index tags >

[jira] [Closed] (OAK-8520) [Direct Binary Access] Avoid overwriting existing binaries via direct binary upload

[ https://issues.apache.org/jira/browse/OAK-8520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta closed OAK-8520. > [Direct Binary Access] Avoid overwriting existing binaries via direct binary > upload >

[jira] [Commented] (OAK-8579) Composite Node Store: Allow creating an index in the read-only repo first

[ https://issues.apache.org/jira/browse/OAK-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917381#comment-16917381 ] Nitin Gupta commented on OAK-8579: -- [~tmueller] - One concern that I have here is we might be 

[jira] [Closed] (OAK-8560) Update jackson-databind dependency to 2.9.9.3

[ https://issues.apache.org/jira/browse/OAK-8560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta closed OAK-8560. > Update jackson-databind dependency to 2.9.9.3 > - > >

[jira] [Closed] (OAK-8597) lc command is unable to construct OakDirectory

[ https://issues.apache.org/jira/browse/OAK-8597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta closed OAK-8597. > lc command is unable to construct OakDirectory > -- > >

[jira] [Closed] (OAK-8599) [Direct Binary Access] Initiate upload should return null if feature is disabled

[ https://issues.apache.org/jira/browse/OAK-8599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta closed OAK-8599. > [Direct Binary Access] Initiate upload should return null if feature is > disabled >

[jira] [Closed] (OAK-8298) [Direct Binary Access] Blobs that are directly uploaded are not tracked by BlobIdTracker

[ https://issues.apache.org/jira/browse/OAK-8298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta closed OAK-8298. > [Direct Binary Access] Blobs that are directly uploaded are not tracked by > BlobIdTracker >

[jira] [Closed] (OAK-8586) Update Oak trunk and 1.10 to Jackrabbit 2.18.3

[ https://issues.apache.org/jira/browse/OAK-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta closed OAK-8586. > Update Oak trunk and 1.10 to Jackrabbit 2.18.3 > -- > >

[jira] [Closed] (OAK-8532) Osgi based test to verify tika setup is working

[ https://issues.apache.org/jira/browse/OAK-8532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta closed OAK-8532. > Osgi based test to verify tika setup is working > --- > >

[jira] [Closed] (OAK-8591) Conflict exception on commit

[ https://issues.apache.org/jira/browse/OAK-8591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta closed OAK-8591. > Conflict exception on commit > > > Key: OAK-8591 >

[jira] [Closed] (OAK-8535) oak-it-osgi fails with encrypted credentials in settings.xml

[ https://issues.apache.org/jira/browse/OAK-8535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta closed OAK-8535. > oak-it-osgi fails with encrypted credentials in settings.xml >

[jira] [Closed] (OAK-8594) Update Oak 1.8 to Jackrabbit 2.16.5

[ https://issues.apache.org/jira/browse/OAK-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta closed OAK-8594. > Update Oak 1.8 to Jackrabbit 2.16.5 > --- > > Key: OAK-8594 >

  1   2   3   4   5   6   7   8   9   >