RE: {DISCUSS} Accumulo quarterly report due Wednesday Oct 12
Thanks Arvind, Brian, Mark, and Dominic for the corrections. The report as submitted is below. Ed Coleman --- submitted report (cut from reporting tool, final formatting may be different) --- ## Description: The Apache Accumulo is a robust, scalable, distributed key/value store with cell-based access control and customizable server-side processing. ## Issues: There are no new issues requiring board attention. The trademark issue with http:www.accumulodata.com is still open and the community is not pursuing action at this time. The domain seems to continue to be automatically renewed even though the owner does not have access to the domain. Unless something changes, we will no longer continue to report on this issue. For historical background information, email from the private list discussing this are at [1], [2] and [3]. No action has been required and allowing the domain to expire was deemed a viable option by Brand Management VP in Jan-2021 (private)[4] to minimize volunteer efforts. ## Membership Data: Apache Accumulo was founded 2012-03-20 (11 years ago) There are currently 41 committers and 41 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Christopher L. Shannon was added to the PMC on 2022-09-26 - Christopher L. Shannon was added as committer on 2022-09-27 ## Project Activity: Project activity on the next release remains active with significant improvements to the current baseline. Currently, Accumulo is targeting an October / November release of version 2.1. We expect to start the release process with an rc0 candidate soon, with the remaining issues being actively worked. The GitHub 2.1 project dashboard is available at [5] and an email discussion is available on thread [6] Current 2.1 progress includes: - 26 pull requests that are currently in progress. - 28 issues that are open, but a lot of these will get bumped to the next version. - 1369 issues that have been resolved. ## Community Health: Overall community health is good and GitHub activity remains consistent. - Community activity remains healthy and centers on GitHub, which is reflected by robust GitHub activity and and offsets the corresponding decrease in email traffic. - Accumulo has transitioned from Jira to GitHub issues. The remaining Jira activity reflects closing obsolete issues. ## Links (private) [1]:https://lists.apache.org/thread.html/r8c8ef5575b14accb6fc00d670764a313b91d76033f761c6e5c7eb29d%40%3Cprivate.accumulo.apache.org%3E (private) [2]:https://lists.apache.org/thread.html/514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6@%3Cprivate.accumulo.apache.org%3E (private) [3]:https://lists.apache.org/thread.html/rcc8c07db43222e08b9992fd739b8f24d18569ba9af3decfdb52c4a3e%40%3Cprivate.accumulo.apache.org%3E (private) [4]:https://lists.apache.org/thread.html/r408e3eed907e3ad24a7c84b5247f51973a4c965c891b01215e45ee17%40%3Cprivate.accumulo.apache.org%3E [5]: https://github.com/apache/accumulo/projects/3 [6]: https://lists.apache.org/thread/0nx7ml312v13chdk6xgcwn0vryr5v0xc -Original Message- From: Dominic Garguilo Sent: Wednesday, October 12, 2022 9:03 AM To: dev@accumulo.apache.org Subject: Re: {DISCUSS} Accumulo quarterly report due Wednesday Oct 12 Hi Ed, Looks good to me once the other concerns are addressed. One more small thing in the second bullet point in community health it looks like there is a repeated word: "The remaining Jira activity reflects closing obsolete *issues.issues*." On Wed, Oct 12, 2022 at 8:21 AM Mark Owens wrote: > Hi Ed, > > Looks good! One other minor grammatical issue: > > We expect to start the release process with an rc0 candidate soon, > with the remaining issues be actively worked. > > I think "be actively" should be "being actively". > > > > On Wed, Oct 12, 2022 at 6:25 AM Brian Loss wrote: > > > LGTM too, but another nit… > > “Community activity remains healthy and centers on GitHub, which is > reflect > > by robust GitHub activity and a corresponding decrease in email > traffic.” > > > > Should that say “is reflected by” instead? > > > > > On Oct 11, 2022, at 8:50 PM, Arvind Shyamsundar < > arvin...@microsoft.com.invalid> > > wrote: > > > > > > Hi Ed, thank you for drafting this. There's a minor typo - "no > > persuing" -> I guess that should be "is not pursuing"? > > > > > > Otherwise, it LGTM. > > > > > > Thank you again. > > > > > > - Arvind Shyamsundar (HE / HIM) > > > > > > -Original Message- > > > From: dev1 > > > Sent: Tuesday, October 11, 2022 5:46 PM > > > To: dev@accumulo.apache.org > > > Subject: [EXTERNAL] {DISCUSS} Accumulo quarterly report due > > > Wednesday
Re: {DISCUSS} Accumulo quarterly report due Wednesday Oct 12
Hi Ed, Looks good to me once the other concerns are addressed. One more small thing in the second bullet point in community health it looks like there is a repeated word: "The remaining Jira activity reflects closing obsolete *issues.issues*." On Wed, Oct 12, 2022 at 8:21 AM Mark Owens wrote: > Hi Ed, > > Looks good! One other minor grammatical issue: > > We expect to start the release process with an rc0 candidate soon, with the > remaining issues be actively worked. > > I think "be actively" should be "being actively". > > > > On Wed, Oct 12, 2022 at 6:25 AM Brian Loss wrote: > > > LGTM too, but another nit… > > “Community activity remains healthy and centers on GitHub, which is > reflect > > by robust GitHub activity and a corresponding decrease in email > traffic.” > > > > Should that say “is reflected by” instead? > > > > > On Oct 11, 2022, at 8:50 PM, Arvind Shyamsundar < > arvin...@microsoft.com.invalid> > > wrote: > > > > > > Hi Ed, thank you for drafting this. There's a minor typo - "no > > persuing" -> I guess that should be "is not pursuing"? > > > > > > Otherwise, it LGTM. > > > > > > Thank you again. > > > > > > - Arvind Shyamsundar (HE / HIM) > > > > > > -Original Message- > > > From: dev1 > > > Sent: Tuesday, October 11, 2022 5:46 PM > > > To: dev@accumulo.apache.org > > > Subject: [EXTERNAL] {DISCUSS} Accumulo quarterly report due Wednesday > > Oct 12 > > > > > > The Apache Accumulo quarterly report is due Wednesday, Oct 12. The > > community decided to publicly prepare the report on the dev mailing list. > > Below is the current draft. (note: This is a cut-n-paste from the report > > wizard, so there may be formatting differences that will not appear when > > the report is submitted via the apache reporting tool.) > > > > > > draft report --- > > > > > > ## Description: > > > The Apache Accumulo is a robust, scalable, distributed key/value store > > with cell-based access control and customizable server-side processing. > > > > > > ## Issues: > > > There are no new issues requiring board attention. > > > > > > The trademark issue with http:www.accumulodata.com is still open and > > the community no persuing action at this time. The domain seems to > continue > > to be automatically renewed even though the owner does not have access to > > the domain. Unless something changes, we will no longer continue to > report > > on this issue. > > > > > > For historical background information, email from the private list > > discussing this are at [1], [2] and [3]. No action has been required and > > allowing the domain to expire was deemed a viable option by Brand > > Management VP in Jan-2021 (private)[4] to minimize volunteer efforts. > > > > > > ## Membership Data: > > > Apache Accumulo was founded 2012-03-20 (11 years ago) There are > > currently 41 committers and 41 PMC members in this project. > > > The Committer-to-PMC ratio is 1:1. > > > > > > Community changes, past quarter: > > > - Christopher L. Shannon was added to the PMC on 2022-09-26 > > > - Christopher L. Shannon was added as committer on 2022-09-27 > > > > > > ## Project Activity: > > > Project activity on the next release remains active with significant > > improvements to the current baseline. Currently, Accumulo is targeting an > > October / November release of version 2.1. We expect to start the > release > > process with an rc0 candidate soon, with the remaining issues be actively > > worked. The GitHub 2.1 project dashboard is available at [5] and an email > > discussion is available on thread [6] > > > > > > Current 2.1 progress includes: > > > > > > - 26 pull requests that are currently in progress. > > > - 28 issues that are open, but a lot of these will get bumped to the > > next > > >version. > > > - 1359 issues that have been resolved. > > > > > > ## Community Health: > > > Overall community health is good and GitHub activity remains > consistent. > > > > > > - Community activity remains healthy and centers on GitHub, which is > > reflect > > > by robust GitHub activity and a corresponding decrease in email > traffic. > > > - Accumulo has transitioned from Jira to GitHub issues. The remaining > > Jira > > > activity reflects closing obsolete issues.issues. > > > > > > ## Links > > > (private) [1]: > > > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Fr8c8ef5575b14accb6fc00d670764a313b91d76033f761c6e5c7eb29d%2540%253Cprivate.accumulo.apache.org%253E&data=05%7C01%7Carvindsh%40microsoft.com%7Ccc919d04b85c4d9126bc08daabeb1b30%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638011323521351759%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5DsIJXr8avv6potFhvdycQYLZstwj5FHJHbbjWiQjvY%3D&reserved=0 > > > (private) [2]: > > > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6%40%25
Re: {DISCUSS} Accumulo quarterly report due Wednesday Oct 12
Hi Ed, Looks good! One other minor grammatical issue: We expect to start the release process with an rc0 candidate soon, with the remaining issues be actively worked. I think "be actively" should be "being actively". On Wed, Oct 12, 2022 at 6:25 AM Brian Loss wrote: > LGTM too, but another nit… > “Community activity remains healthy and centers on GitHub, which is reflect > by robust GitHub activity and a corresponding decrease in email traffic.” > > Should that say “is reflected by” instead? > > > On Oct 11, 2022, at 8:50 PM, Arvind Shyamsundar > > > wrote: > > > > Hi Ed, thank you for drafting this. There's a minor typo - "no > persuing" -> I guess that should be "is not pursuing"? > > > > Otherwise, it LGTM. > > > > Thank you again. > > > > - Arvind Shyamsundar (HE / HIM) > > > > -Original Message- > > From: dev1 > > Sent: Tuesday, October 11, 2022 5:46 PM > > To: dev@accumulo.apache.org > > Subject: [EXTERNAL] {DISCUSS} Accumulo quarterly report due Wednesday > Oct 12 > > > > The Apache Accumulo quarterly report is due Wednesday, Oct 12. The > community decided to publicly prepare the report on the dev mailing list. > Below is the current draft. (note: This is a cut-n-paste from the report > wizard, so there may be formatting differences that will not appear when > the report is submitted via the apache reporting tool.) > > > > draft report --- > > > > ## Description: > > The Apache Accumulo is a robust, scalable, distributed key/value store > with cell-based access control and customizable server-side processing. > > > > ## Issues: > > There are no new issues requiring board attention. > > > > The trademark issue with http:www.accumulodata.com is still open and > the community no persuing action at this time. The domain seems to continue > to be automatically renewed even though the owner does not have access to > the domain. Unless something changes, we will no longer continue to report > on this issue. > > > > For historical background information, email from the private list > discussing this are at [1], [2] and [3]. No action has been required and > allowing the domain to expire was deemed a viable option by Brand > Management VP in Jan-2021 (private)[4] to minimize volunteer efforts. > > > > ## Membership Data: > > Apache Accumulo was founded 2012-03-20 (11 years ago) There are > currently 41 committers and 41 PMC members in this project. > > The Committer-to-PMC ratio is 1:1. > > > > Community changes, past quarter: > > - Christopher L. Shannon was added to the PMC on 2022-09-26 > > - Christopher L. Shannon was added as committer on 2022-09-27 > > > > ## Project Activity: > > Project activity on the next release remains active with significant > improvements to the current baseline. Currently, Accumulo is targeting an > October / November release of version 2.1. We expect to start the release > process with an rc0 candidate soon, with the remaining issues be actively > worked. The GitHub 2.1 project dashboard is available at [5] and an email > discussion is available on thread [6] > > > > Current 2.1 progress includes: > > > > - 26 pull requests that are currently in progress. > > - 28 issues that are open, but a lot of these will get bumped to the > next > >version. > > - 1359 issues that have been resolved. > > > > ## Community Health: > > Overall community health is good and GitHub activity remains consistent. > > > > - Community activity remains healthy and centers on GitHub, which is > reflect > > by robust GitHub activity and a corresponding decrease in email traffic. > > - Accumulo has transitioned from Jira to GitHub issues. The remaining > Jira > > activity reflects closing obsolete issues.issues. > > > > ## Links > > (private) [1]: > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Fr8c8ef5575b14accb6fc00d670764a313b91d76033f761c6e5c7eb29d%2540%253Cprivate.accumulo.apache.org%253E&data=05%7C01%7Carvindsh%40microsoft.com%7Ccc919d04b85c4d9126bc08daabeb1b30%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638011323521351759%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5DsIJXr8avv6potFhvdycQYLZstwj5FHJHbbjWiQjvY%3D&reserved=0 > > (private) [2]: > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6%40%253Cprivate.accumulo.apache.org%253E&data=05%7C01%7Carvindsh%40microsoft.com%7Ccc919d04b85c4d9126bc08daabeb1b30%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638011323521351759%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Pjx4zZxtKL0rPYn8dyZMXbcwIHaiV9FZmKoWp%2BHHTSk%3D&reserved=0 > > (private) [3]: > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Frcc8c07db43222e08b9992fd739b8f24d18569ba9af3decfdb52c4a3e%2540%253Cprivate.accumul
Re: {DISCUSS} Accumulo quarterly report due Wednesday Oct 12
LGTM too, but another nit… “Community activity remains healthy and centers on GitHub, which is reflect by robust GitHub activity and a corresponding decrease in email traffic.” Should that say “is reflected by” instead? > On Oct 11, 2022, at 8:50 PM, Arvind Shyamsundar > wrote: > > Hi Ed, thank you for drafting this. There's a minor typo - "no persuing" -> > I guess that should be "is not pursuing"? > > Otherwise, it LGTM. > > Thank you again. > > - Arvind Shyamsundar (HE / HIM) > > -Original Message- > From: dev1 > Sent: Tuesday, October 11, 2022 5:46 PM > To: dev@accumulo.apache.org > Subject: [EXTERNAL] {DISCUSS} Accumulo quarterly report due Wednesday Oct 12 > > The Apache Accumulo quarterly report is due Wednesday, Oct 12. The community > decided to publicly prepare the report on the dev mailing list. Below is the > current draft. (note: This is a cut-n-paste from the report wizard, so there > may be formatting differences that will not appear when the report is > submitted via the apache reporting tool.) > > draft report --- > > ## Description: > The Apache Accumulo is a robust, scalable, distributed key/value store with > cell-based access control and customizable server-side processing. > > ## Issues: > There are no new issues requiring board attention. > > The trademark issue with http:www.accumulodata.com is still open and the > community no persuing action at this time. The domain seems to continue to be > automatically renewed even though the owner does not have access to the > domain. Unless something changes, we will no longer continue to report on > this issue. > > For historical background information, email from the private list discussing > this are at [1], [2] and [3]. No action has been required and allowing the > domain to expire was deemed a viable option by Brand Management VP in > Jan-2021 (private)[4] to minimize volunteer efforts. > > ## Membership Data: > Apache Accumulo was founded 2012-03-20 (11 years ago) There are currently 41 > committers and 41 PMC members in this project. > The Committer-to-PMC ratio is 1:1. > > Community changes, past quarter: > - Christopher L. Shannon was added to the PMC on 2022-09-26 > - Christopher L. Shannon was added as committer on 2022-09-27 > > ## Project Activity: > Project activity on the next release remains active with significant > improvements to the current baseline. Currently, Accumulo is targeting an > October / November release of version 2.1. We expect to start the release > process with an rc0 candidate soon, with the remaining issues be actively > worked. The GitHub 2.1 project dashboard is available at [5] and an email > discussion is available on thread [6] > > Current 2.1 progress includes: > > - 26 pull requests that are currently in progress. > - 28 issues that are open, but a lot of these will get bumped to the next >version. > - 1359 issues that have been resolved. > > ## Community Health: > Overall community health is good and GitHub activity remains consistent. > > - Community activity remains healthy and centers on GitHub, which is reflect > by robust GitHub activity and a corresponding decrease in email traffic. > - Accumulo has transitioned from Jira to GitHub issues. The remaining Jira > activity reflects closing obsolete issues.issues. > > ## Links > (private) > [1]:https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Fr8c8ef5575b14accb6fc00d670764a313b91d76033f761c6e5c7eb29d%2540%253Cprivate.accumulo.apache.org%253E&data=05%7C01%7Carvindsh%40microsoft.com%7Ccc919d04b85c4d9126bc08daabeb1b30%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638011323521351759%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5DsIJXr8avv6potFhvdycQYLZstwj5FHJHbbjWiQjvY%3D&reserved=0 > (private) > [2]:https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6%40%253Cprivate.accumulo.apache.org%253E&data=05%7C01%7Carvindsh%40microsoft.com%7Ccc919d04b85c4d9126bc08daabeb1b30%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638011323521351759%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Pjx4zZxtKL0rPYn8dyZMXbcwIHaiV9FZmKoWp%2BHHTSk%3D&reserved=0 > (private) > [3]:https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Frcc8c07db43222e08b9992fd739b8f24d18569ba9af3decfdb52c4a3e%2540%253Cprivate.accumulo.apache.org%253E&data=05%7C01%7Carvindsh%40microsoft.com%7Ccc919d04b85c4d9126bc08daabeb1b30%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638011323521351759%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g5v8LzyQ1NzVwhwrV3oANOi8W7UJ7%2B4pkduUiHpi81o%3D&reserved=0 > (private) > [4]:https://nam06.safelinks.pro
RE: {DISCUSS} Accumulo quarterly report due Wednesday Oct 12
Hi Ed, thank you for drafting this. There's a minor typo - "no persuing" -> I guess that should be "is not pursuing"? Otherwise, it LGTM. Thank you again. - Arvind Shyamsundar (HE / HIM) -Original Message- From: dev1 Sent: Tuesday, October 11, 2022 5:46 PM To: dev@accumulo.apache.org Subject: [EXTERNAL] {DISCUSS} Accumulo quarterly report due Wednesday Oct 12 The Apache Accumulo quarterly report is due Wednesday, Oct 12. The community decided to publicly prepare the report on the dev mailing list. Below is the current draft. (note: This is a cut-n-paste from the report wizard, so there may be formatting differences that will not appear when the report is submitted via the apache reporting tool.) draft report --- ## Description: The Apache Accumulo is a robust, scalable, distributed key/value store with cell-based access control and customizable server-side processing. ## Issues: There are no new issues requiring board attention. The trademark issue with http:www.accumulodata.com is still open and the community no persuing action at this time. The domain seems to continue to be automatically renewed even though the owner does not have access to the domain. Unless something changes, we will no longer continue to report on this issue. For historical background information, email from the private list discussing this are at [1], [2] and [3]. No action has been required and allowing the domain to expire was deemed a viable option by Brand Management VP in Jan-2021 (private)[4] to minimize volunteer efforts. ## Membership Data: Apache Accumulo was founded 2012-03-20 (11 years ago) There are currently 41 committers and 41 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - Christopher L. Shannon was added to the PMC on 2022-09-26 - Christopher L. Shannon was added as committer on 2022-09-27 ## Project Activity: Project activity on the next release remains active with significant improvements to the current baseline. Currently, Accumulo is targeting an October / November release of version 2.1. We expect to start the release process with an rc0 candidate soon, with the remaining issues be actively worked. The GitHub 2.1 project dashboard is available at [5] and an email discussion is available on thread [6] Current 2.1 progress includes: - 26 pull requests that are currently in progress. - 28 issues that are open, but a lot of these will get bumped to the next version. - 1359 issues that have been resolved. ## Community Health: Overall community health is good and GitHub activity remains consistent. - Community activity remains healthy and centers on GitHub, which is reflect by robust GitHub activity and a corresponding decrease in email traffic. - Accumulo has transitioned from Jira to GitHub issues. The remaining Jira activity reflects closing obsolete issues.issues. ## Links (private) [1]:https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Fr8c8ef5575b14accb6fc00d670764a313b91d76033f761c6e5c7eb29d%2540%253Cprivate.accumulo.apache.org%253E&data=05%7C01%7Carvindsh%40microsoft.com%7Ccc919d04b85c4d9126bc08daabeb1b30%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638011323521351759%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5DsIJXr8avv6potFhvdycQYLZstwj5FHJHbbjWiQjvY%3D&reserved=0 (private) [2]:https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F514d3cf9162e72f4aa13be1db5d6685999fc83755695308a529de4d6%40%253Cprivate.accumulo.apache.org%253E&data=05%7C01%7Carvindsh%40microsoft.com%7Ccc919d04b85c4d9126bc08daabeb1b30%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638011323521351759%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Pjx4zZxtKL0rPYn8dyZMXbcwIHaiV9FZmKoWp%2BHHTSk%3D&reserved=0 (private) [3]:https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Frcc8c07db43222e08b9992fd739b8f24d18569ba9af3decfdb52c4a3e%2540%253Cprivate.accumulo.apache.org%253E&data=05%7C01%7Carvindsh%40microsoft.com%7Ccc919d04b85c4d9126bc08daabeb1b30%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638011323521351759%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g5v8LzyQ1NzVwhwrV3oANOi8W7UJ7%2B4pkduUiHpi81o%3D&reserved=0 (private) [4]:https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Fr408e3eed907e3ad24a7c84b5247f51973a4c965c891b01215e45ee17%2540%253Cprivate.accumulo.apache.org%253E&data=05%7C01%7Carvindsh%40microsoft.com%7Ccc919d04b85c4d9126bc08daabeb1b30%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638011323521351759%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uHwoJzK25bt3DVWetqrYkI0