You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@drill.apache.org by luoc <lu...@apache.org> on 2021/11/01 14:27:11 UTC
Drill 1.20 release plan
Hello, Drill dev and users :
Since the latest 1.19, Drill master branch has collected many changes, bug fixed and enhanced. Drill team plan to release the 1.20 at the end of November 2021.
We have some things to work out :
1. Are you willing to be the 1.20 release manager?
2. Is there one of the unmerged pull request that you want to complete?
3. Do you have a feature under development and want to include in 1.20?
4. Would you like to help with the test and feedback (build with master branch)?
I hope everyone will participate in the talk and reply to these questions as soon as possible, thank you.
-- luoc
Re: Drill 1.20 release plan
Posted by luoc <lu...@apache.org>.
Thank you, Charles. I can see you everywhere.
The most competent PMC Chair.
> 在 2021年11月3日，21:24，Charles Givre <cg...@gmail.com> 写道：
> Hi Luoc,
> IMHO there are a few PRs in flight that I’d like to see included in the next release. I sent them in slack, but so that they are preserved for the mailing list. I'd like to see DRILL-1282, DRILL-7938, DRILL-8027, DRILL-8028 and possibly DRILL-8009 and DRILL-7978 get merged for the next release. DRILL-7871 would be a stretch goal.
> Best,
> — C
>
>> On Nov 3, 2021, at 9:21 AM, luoc <lu...@apache.org> wrote:
>>
>>
>> Thanks for your support, James. Since there are no negative votes, I will recommend you as the release manager.
>>
>> We'll keep a light on for you.
>>
>>>> 在 2021年11月3日，01:04，James Turton <ja...@somecomputer.xyz> 写道：
>>> Hi luoc
>>> I am willing to help the release in any capacity needed. I know there are others who have release experience while I do not but I'm sure it can be learned. I'll have PR #2351 done this week, it would be nice (but not critical) to include it.
>>> Thanks
>>> James
>>>> On 2021/11/01 16:27, luoc wrote:
>>>>
>>>> Hello, Drill dev and users :
>>>> Since the latest 1.19, Drill master branch has collected many changes, bug fixed and enhanced. Drill team plan to release the 1.20 at the end of November 2021.
>>>> We have some things to work out :
>>>> 1. Are you willing to be the 1.20 release manager?
>>>> 2. Is there one of the unmerged pull request that you want to complete?
>>>> 3. Do you have a feature under development and want to include in 1.20?
>>>> 4. Would you like to help with the test and feedback (build with master branch)?
>>>> I hope everyone will participate in the talk and reply to these questions as soon as possible, thank you.
>>>> -- luoc
Re: Drill 1.20 release plan
Posted by luoc <lu...@apache.org>.
Thank you, Charles. I can see you everywhere.
The most competent PMC Chair.
> 在 2021年11月3日，21:24，Charles Givre <cg...@gmail.com> 写道：
> Hi Luoc,
> IMHO there are a few PRs in flight that I’d like to see included in the next release. I sent them in slack, but so that they are preserved for the mailing list. I'd like to see DRILL-1282, DRILL-7938, DRILL-8027, DRILL-8028 and possibly DRILL-8009 and DRILL-7978 get merged for the next release. DRILL-7871 would be a stretch goal.
> Best,
> — C
>
>> On Nov 3, 2021, at 9:21 AM, luoc <lu...@apache.org> wrote:
>>
>>
>> Thanks for your support, James. Since there are no negative votes, I will recommend you as the release manager.
>>
>> We'll keep a light on for you.
>>
>>>> 在 2021年11月3日，01:04，James Turton <ja...@somecomputer.xyz> 写道：
>>> Hi luoc
>>> I am willing to help the release in any capacity needed. I know there are others who have release experience while I do not but I'm sure it can be learned. I'll have PR #2351 done this week, it would be nice (but not critical) to include it.
>>> Thanks
>>> James
>>>> On 2021/11/01 16:27, luoc wrote:
>>>>
>>>> Hello, Drill dev and users :
>>>> Since the latest 1.19, Drill master branch has collected many changes, bug fixed and enhanced. Drill team plan to release the 1.20 at the end of November 2021.
>>>> We have some things to work out :
>>>> 1. Are you willing to be the 1.20 release manager?
>>>> 2. Is there one of the unmerged pull request that you want to complete?
>>>> 3. Do you have a feature under development and want to include in 1.20?
>>>> 4. Would you like to help with the test and feedback (build with master branch)?
>>>> I hope everyone will participate in the talk and reply to these questions as soon as possible, thank you.
>>>> -- luoc
Re: Drill 1.20 release plan
Posted by luoc <lu...@apache.org>.
Hi James,
Is there a ticket related to Calcite?
> 在 2021年12月1日，21:14，James Turton <dz...@apache.org> 写道：
> We've picked up a bug: DRILL-8063. It was present in earlier releases (verified in 1.18) and may require a fix in Calcite rather than our own codebase. It's a severe one, resulting in an OOM crash for particular queries. Please indicate if you would like to have the following marked as a release blocker. Lazy consensus will apply, i.e. no reply = "I do not believe this bug should block 1.20".
>
> https://issues.apache.org/jira/browse/DRILL-8063
>
>
>> On 2021/12/01 12:00, James Turton wrote:
>> Hi all
>>
>> Given we've had no objections, please strive to merge your PRs for 1.20 by 10 December which is the current targeted freeze date.
>>
>> Closed:
>> DRILL-1282 Parquet v2 read+write
>> DRILL-8027 Iceberg format
>> DRILL-8009 JDBC isValid()
>>
>> Open:
>> DRILL-7863 Phoenix storage
>> DRILL-7978 Fixed width format
>> DRILL-7983 Get running/completed profiles from REST API
>> DRILL-8015 MongoDB Metastore
>> DRILL-8028 PDF format
>> * DRILL-8057 INFORMATION_SCHEMA filter push down is inefficient (feasibility not yet clear)
>>
>>
>>> On 2021/11/25 09:53, James Turton wrote:
>>> Dear dev community
>>> Please see an update on the Jiras earmarked for 1.20 below. We have of course also closed other Jiras in the intervening period. If you are aware of any reason that one of the listed Jiras will not be ready please say so, so I can remove it. Otherwise I'll post comments to the authors asking them to aim for merging by the release cut-off date. How does a cut-off date of 10 December sound?
>>> (* indicates a Jira not previously discussed in this thread.)
>>> Closed:
>>> DRILL-1282 Parquet v2 read+write
>>> DRILL-8027 Iceberg format
>>> Open:
>>> DRILL-7863 Phoenix storage
>>> DRILL-7978 Fixed width format
>>> DRILL-7983 Get running/completed profiles from REST API (corrected from 7938 which I believe was a typo)
>>> DRILL-8009 JDBC isValid()
>>> * DRILL-8015 MongoDB Metastore
>>> DRILL-8028 PDF format
>>> The stretch goal DRILL-7871 (StoragePluginStore instance per user) has not yet reached design consensus so I propose that it should not be included in 1.20.
>>> On 2021/11/03 15:24, Charles Givre wrote:
>>>> Hi Luoc,
>>>> IMHO there are a few PRs in flight that I’d like to see included in the next release. I sent them in slack, but so that they are preserved for the mailing list. I'd like to see DRILL-1282, DRILL-7938, DRILL-8027, DRILL-8028 and possibly DRILL-8009 and DRILL-7978 get merged for the next release. DRILL-7871 would be a stretch goal.
>>>> Best,
>>>> — C
>>>>> On Nov 3, 2021, at 9:21 AM, luoc <lu...@apache.org> wrote:
>>>>> Thanks for your support, James. Since there are no negative votes, I will recommend you as the release manager.
>>>>> We'll keep a light on for you.
>>>>>> 在 2021年11月3日，01:04，James Turton <ja...@somecomputer.xyz> 写道：
>>>>>> Hi luoc
>>>>>> I am willing to help the release in any capacity needed. I know there are others who have release experience while I do not but I'm sure it can be learned. I'll have PR #2351 done this week, it would be nice (but not critical) to include it.
>>>>>> Thanks
>>>>>> James
>>>>>>> On 2021/11/01 16:27, luoc wrote:
>>>>>>>
>>>>>>> Hello, Drill dev and users :
>>>>>>> Since the latest 1.19, Drill master branch has collected many changes, bug fixed and enhanced. Drill team plan to release the 1.20 at the end of November 2021.
>>>>>>> We have some things to work out :
>>>>>>> 1. Are you willing to be the 1.20 release manager?
>>>>>>> 2. Is there one of the unmerged pull request that you want to complete?
>>>>>>> 3. Do you have a feature under development and want to include in 1.20?
>>>>>>> 4. Would you like to help with the test and feedback (build with master branch)?
>>>>>>> I hope everyone will participate in the talk and reply to these questions as soon as possible, thank you.
>>>>>>> -- luoc
>
> <dzamo.vcf>
Re: Drill 1.20 release plan
Posted by James Turton <dz...@apache.org>.
Okay, good idea.
@luoc: I believe that there have been a number of "infinite planning"
bugs found and fixed in Calcite. It's beyond my Calcite knowledge to be
able to tell if any one of them covers this particular issue...
On 2021/12/01 15:34, Charles Givre wrote:
> My vote here would be to do a bit of diagnosis first. Let's see if we can figure out what is going wrong and a sense of how much effort is required to fix. Once we know that, we can decide on how to proceed.
> -- C
>
>
>> On Dec 1, 2021, at 8:13 AM, James Turton <dz...@apache.org> wrote:
>>
>> We've picked up a bug: DRILL-8063. It was present in earlier releases (verified in 1.18) and may require a fix in Calcite rather than our own codebase. It's a severe one, resulting in an OOM crash for particular queries. Please indicate if you would like to have the following marked as a release blocker. Lazy consensus will apply, i.e. no reply = "I do not believe this bug should block 1.20".
>>
>> https://issues.apache.org/jira/browse/DRILL-8063
>>
>>
>> On 2021/12/01 12:00, James Turton wrote:
>>> Hi all
>>>
>>> Given we've had no objections, please strive to merge your PRs for 1.20 by 10 December which is the current targeted freeze date.
>>>
>>> Closed:
>>> DRILL-1282 Parquet v2 read+write
>>> DRILL-8027 Iceberg format
>>> DRILL-8009 JDBC isValid()
>>>
>>> Open:
>>> DRILL-7863 Phoenix storage
>>> DRILL-7978 Fixed width format
>>> DRILL-7983 Get running/completed profiles from REST API
>>> DRILL-8015 MongoDB Metastore
>>> DRILL-8028 PDF format
>>> * DRILL-8057 INFORMATION_SCHEMA filter push down is inefficient (feasibility not yet clear)
>>>
>>>
>>> On 2021/11/25 09:53, James Turton wrote:
>>>> Dear dev community
>>>>
>>>> Please see an update on the Jiras earmarked for 1.20 below. We have of course also closed other Jiras in the intervening period. If you are aware of any reason that one of the listed Jiras will not be ready please say so, so I can remove it. Otherwise I'll post comments to the authors asking them to aim for merging by the release cut-off date. How does a cut-off date of 10 December sound?
>>>>
>>>> (* indicates a Jira not previously discussed in this thread.)
>>>>
>>>> Closed:
>>>> DRILL-1282 Parquet v2 read+write
>>>> DRILL-8027 Iceberg format
>>>>
>>>> Open:
>>>> DRILL-7863 Phoenix storage
>>>> DRILL-7978 Fixed width format
>>>> DRILL-7983 Get running/completed profiles from REST API (corrected from 7938 which I believe was a typo)
>>>> DRILL-8009 JDBC isValid()
>>>> * DRILL-8015 MongoDB Metastore
>>>> DRILL-8028 PDF format
>>>>
>>>>
>>>> The stretch goal DRILL-7871 (StoragePluginStore instance per user) has not yet reached design consensus so I propose that it should not be included in 1.20.
>>>>
>>>>
>>>> On 2021/11/03 15:24, Charles Givre wrote:
>>>>> Hi Luoc,
>>>>> IMHO there are a few PRs in flight that I’d like to see included in the next release. I sent them in slack, but so that they are preserved for the mailing list. I'd like to see DRILL-1282, DRILL-7938, DRILL-8027, DRILL-8028 and possibly DRILL-8009 and DRILL-7978 get merged for the next release. DRILL-7871 would be a stretch goal.
>>>>> Best,
>>>>> — C
>>>>>
>>>>>> On Nov 3, 2021, at 9:21 AM, luoc <lu...@apache.org> wrote:
>>>>>>
>>>>>>
>>>>>> Thanks for your support, James. Since there are no negative votes, I will recommend you as the release manager.
>>>>>>
>>>>>> We'll keep a light on for you.
>>>>>>
>>>>>>> 在 2021年11月3日，01:04，James Turton <ja...@somecomputer.xyz> 写道：
>>>>>>>
>>>>>>> Hi luoc
>>>>>>>
>>>>>>> I am willing to help the release in any capacity needed. I know there are others who have release experience while I do not but I'm sure it can be learned. I'll have PR #2351 done this week, it would be nice (but not critical) to include it.
>>>>>>>
>>>>>>> Thanks
>>>>>>> James
>>>>>>>
>>>>>>>> On 2021/11/01 16:27, luoc wrote:
>>>>>>>>
>>>>>>>> Hello, Drill dev and users :
>>>>>>>>
>>>>>>>> Since the latest 1.19, Drill master branch has collected many changes, bug fixed and enhanced. Drill team plan to release the 1.20 at the end of November 2021.
>>>>>>>>
>>>>>>>> We have some things to work out :
>>>>>>>>
>>>>>>>> 1. Are you willing to be the 1.20 release manager?
>>>>>>>>
>>>>>>>> 2. Is there one of the unmerged pull request that you want to complete?
>>>>>>>>
>>>>>>>> 3. Do you have a feature under development and want to include in 1.20?
>>>>>>>>
>>>>>>>> 4. Would you like to help with the test and feedback (build with master branch)?
>>>>>>>>
>>>>>>>> I hope everyone will participate in the talk and reply to these questions as soon as possible, thank you.
>>>>>>>>
>>>>>>>> -- luoc
>>>>>>>>
>>>>>>>>
>> <dzamo.vcf>
Re: Drill 1.20 release plan
Posted by Charles Givre <cg...@gmail.com>.
My vote here would be to do a bit of diagnosis first. Let's see if we can figure out what is going wrong and a sense of how much effort is required to fix. Once we know that, we can decide on how to proceed.
-- C
> On Dec 1, 2021, at 8:13 AM, James Turton <dz...@apache.org> wrote:
>
> We've picked up a bug: DRILL-8063. It was present in earlier releases (verified in 1.18) and may require a fix in Calcite rather than our own codebase. It's a severe one, resulting in an OOM crash for particular queries. Please indicate if you would like to have the following marked as a release blocker. Lazy consensus will apply, i.e. no reply = "I do not believe this bug should block 1.20".
>
> https://issues.apache.org/jira/browse/DRILL-8063
>
>
> On 2021/12/01 12:00, James Turton wrote:
>> Hi all
>>
>> Given we've had no objections, please strive to merge your PRs for 1.20 by 10 December which is the current targeted freeze date.
>>
>> Closed:
>> DRILL-1282 Parquet v2 read+write
>> DRILL-8027 Iceberg format
>> DRILL-8009 JDBC isValid()
>>
>> Open:
>> DRILL-7863 Phoenix storage
>> DRILL-7978 Fixed width format
>> DRILL-7983 Get running/completed profiles from REST API
>> DRILL-8015 MongoDB Metastore
>> DRILL-8028 PDF format
>> * DRILL-8057 INFORMATION_SCHEMA filter push down is inefficient (feasibility not yet clear)
>>
>>
>> On 2021/11/25 09:53, James Turton wrote:
>>> Dear dev community
>>>
>>> Please see an update on the Jiras earmarked for 1.20 below. We have of course also closed other Jiras in the intervening period. If you are aware of any reason that one of the listed Jiras will not be ready please say so, so I can remove it. Otherwise I'll post comments to the authors asking them to aim for merging by the release cut-off date. How does a cut-off date of 10 December sound?
>>>
>>> (* indicates a Jira not previously discussed in this thread.)
>>>
>>> Closed:
>>> DRILL-1282 Parquet v2 read+write
>>> DRILL-8027 Iceberg format
>>>
>>> Open:
>>> DRILL-7863 Phoenix storage
>>> DRILL-7978 Fixed width format
>>> DRILL-7983 Get running/completed profiles from REST API (corrected from 7938 which I believe was a typo)
>>> DRILL-8009 JDBC isValid()
>>> * DRILL-8015 MongoDB Metastore
>>> DRILL-8028 PDF format
>>>
>>>
>>> The stretch goal DRILL-7871 (StoragePluginStore instance per user) has not yet reached design consensus so I propose that it should not be included in 1.20.
>>>
>>>
>>> On 2021/11/03 15:24, Charles Givre wrote:
>>>> Hi Luoc,
>>>> IMHO there are a few PRs in flight that I’d like to see included in the next release. I sent them in slack, but so that they are preserved for the mailing list. I'd like to see DRILL-1282, DRILL-7938, DRILL-8027, DRILL-8028 and possibly DRILL-8009 and DRILL-7978 get merged for the next release. DRILL-7871 would be a stretch goal.
>>>> Best,
>>>> — C
>>>>
>>>>> On Nov 3, 2021, at 9:21 AM, luoc <lu...@apache.org> wrote:
>>>>>
>>>>>
>>>>> Thanks for your support, James. Since there are no negative votes, I will recommend you as the release manager.
>>>>>
>>>>> We'll keep a light on for you.
>>>>>
>>>>>> 在 2021年11月3日，01:04，James Turton <ja...@somecomputer.xyz> 写道：
>>>>>>
>>>>>> Hi luoc
>>>>>>
>>>>>> I am willing to help the release in any capacity needed. I know there are others who have release experience while I do not but I'm sure it can be learned. I'll have PR #2351 done this week, it would be nice (but not critical) to include it.
>>>>>>
>>>>>> Thanks
>>>>>> James
>>>>>>
>>>>>>> On 2021/11/01 16:27, luoc wrote:
>>>>>>>
>>>>>>> Hello, Drill dev and users :
>>>>>>>
>>>>>>> Since the latest 1.19, Drill master branch has collected many changes, bug fixed and enhanced. Drill team plan to release the 1.20 at the end of November 2021.
>>>>>>>
>>>>>>> We have some things to work out :
>>>>>>>
>>>>>>> 1. Are you willing to be the 1.20 release manager?
>>>>>>>
>>>>>>> 2. Is there one of the unmerged pull request that you want to complete?
>>>>>>>
>>>>>>> 3. Do you have a feature under development and want to include in 1.20?
>>>>>>>
>>>>>>> 4. Would you like to help with the test and feedback (build with master branch)?
>>>>>>>
>>>>>>> I hope everyone will participate in the talk and reply to these questions as soon as possible, thank you.
>>>>>>>
>>>>>>> -- luoc
>>>>>>>
>>>>>>>
> <dzamo.vcf>
Re: Drill 1.20 release plan
Posted by James Turton <dz...@apache.org>.
We've picked up a bug: DRILL-8063. It was present in earlier releases
(verified in 1.18) and may require a fix in Calcite rather than our own
codebase. It's a severe one, resulting in an OOM crash for particular
queries. Please indicate if you would like to have the following marked
as a release blocker. Lazy consensus will apply, i.e. no reply = "I do
not believe this bug should block 1.20".
https://issues.apache.org/jira/browse/DRILL-8063
On 2021/12/01 12:00, James Turton wrote:
> Hi all
>
> Given we've had no objections, please strive to merge your PRs for
> 1.20 by 10 December which is the current targeted freeze date.
>
> Closed:
> DRILL-1282 Parquet v2 read+write
> DRILL-8027 Iceberg format
> DRILL-8009 JDBC isValid()
>
> Open:
> DRILL-7863 Phoenix storage
> DRILL-7978 Fixed width format
> DRILL-7983 Get running/completed profiles from REST API
> DRILL-8015 MongoDB Metastore
> DRILL-8028 PDF format
> * DRILL-8057 INFORMATION_SCHEMA filter push down is inefficient
> (feasibility not yet clear)
>
>
> On 2021/11/25 09:53, James Turton wrote:
>> Dear dev community
>>
>> Please see an update on the Jiras earmarked for 1.20 below. We have
>> of course also closed other Jiras in the intervening period. If you
>> are aware of any reason that one of the listed Jiras will not be
>> ready please say so, so I can remove it. Otherwise I'll post comments
>> to the authors asking them to aim for merging by the release cut-off
>> date. How does a cut-off date of 10 December sound?
>>
>> (* indicates a Jira not previously discussed in this thread.)
>>
>> Closed:
>> DRILL-1282 Parquet v2 read+write
>> DRILL-8027 Iceberg format
>>
>> Open:
>> DRILL-7863 Phoenix storage
>> DRILL-7978 Fixed width format
>> DRILL-7983 Get running/completed profiles from REST API (corrected
>> from 7938 which I believe was a typo)
>> DRILL-8009 JDBC isValid()
>> * DRILL-8015 MongoDB Metastore
>> DRILL-8028 PDF format
>>
>>
>> The stretch goal DRILL-7871 (StoragePluginStore instance per user)
>> has not yet reached design consensus so I propose that it should not
>> be included in 1.20.
>>
>>
>> On 2021/11/03 15:24, Charles Givre wrote:
>>> Hi Luoc,
>>> IMHO there are a few PRs in flight that I’d like to see included in
>>> the next release. I sent them in slack, but so that they are
>>> preserved for the mailing list. I'd like to see DRILL-1282,
>>> DRILL-7938, DRILL-8027, DRILL-8028 and possibly DRILL-8009 and
>>> DRILL-7978 get merged for the next release. DRILL-7871 would be a
>>> stretch goal.
>>> Best,
>>> — C
>>>
>>>> On Nov 3, 2021, at 9:21 AM, luoc <lu...@apache.org> wrote:
>>>>
>>>>
>>>> Thanks for your support, James. Since there are no negative votes,
>>>> I will recommend you as the release manager.
>>>>
>>>> We'll keep a light on for you.
>>>>
>>>>> 在 2021年11月3日，01:04，James Turton <ja...@somecomputer.xyz> 写道：
>>>>>
>>>>> Hi luoc
>>>>>
>>>>> I am willing to help the release in any capacity needed. I know
>>>>> there are others who have release experience while I do not but
>>>>> I'm sure it can be learned. I'll have PR #2351 done this week, it
>>>>> would be nice (but not critical) to include it.
>>>>>
>>>>> Thanks
>>>>> James
>>>>>
>>>>>> On 2021/11/01 16:27, luoc wrote:
>>>>>>
>>>>>> Hello, Drill dev and users :
>>>>>>
>>>>>> Since the latest 1.19, Drill master branch has collected many
>>>>>> changes, bug fixed and enhanced. Drill team plan to release the
>>>>>> 1.20 at the end of November 2021.
>>>>>>
>>>>>> We have some things to work out :
>>>>>>
>>>>>> 1. Are you willing to be the 1.20 release manager?
>>>>>>
>>>>>> 2. Is there one of the unmerged pull request that you want to
>>>>>> complete?
>>>>>>
>>>>>> 3. Do you have a feature under development and want to include in
>>>>>> 1.20?
>>>>>>
>>>>>> 4. Would you like to help with the test and feedback (build with
>>>>>> master branch)?
>>>>>>
>>>>>> I hope everyone will participate in the talk and reply to these
>>>>>> questions as soon as possible, thank you.
>>>>>>
>>>>>> -- luoc
>>>>>>
>>>>>>
Re: Drill 1.20 release plan
Posted by James Turton <dz...@apache.org>.
Hi all
Given we've had no objections, please strive to merge your PRs for 1.20
by 10 December which is the current targeted freeze date.
Closed:
DRILL-1282 Parquet v2 read+write
DRILL-8027 Iceberg format
DRILL-8009 JDBC isValid()
Open:
DRILL-7863 Phoenix storage
DRILL-7978 Fixed width format
DRILL-7983 Get running/completed profiles from REST API
DRILL-8015 MongoDB Metastore
DRILL-8028 PDF format
* DRILL-8057 INFORMATION_SCHEMA filter push down is inefficient
(feasibility not yet clear)
On 2021/11/25 09:53, James Turton wrote:
> Dear dev community
>
> Please see an update on the Jiras earmarked for 1.20 below. We have of
> course also closed other Jiras in the intervening period. If you are
> aware of any reason that one of the listed Jiras will not be ready
> please say so, so I can remove it. Otherwise I'll post comments to
> the authors asking them to aim for merging by the release cut-off
> date. How does a cut-off date of 10 December sound?
>
> (* indicates a Jira not previously discussed in this thread.)
>
> Closed:
> DRILL-1282 Parquet v2 read+write
> DRILL-8027 Iceberg format
>
> Open:
> DRILL-7863 Phoenix storage
> DRILL-7978 Fixed width format
> DRILL-7983 Get running/completed profiles from REST API (corrected
> from 7938 which I believe was a typo)
> DRILL-8009 JDBC isValid()
> * DRILL-8015 MongoDB Metastore
> DRILL-8028 PDF format
>
>
> The stretch goal DRILL-7871 (StoragePluginStore instance per user) has
> not yet reached design consensus so I propose that it should not be
> included in 1.20.
>
>
> On 2021/11/03 15:24, Charles Givre wrote:
>> Hi Luoc,
>> IMHO there are a few PRs in flight that I’d like to see included in
>> the next release. I sent them in slack, but so that they are
>> preserved for the mailing list. I'd like to see DRILL-1282,
>> DRILL-7938, DRILL-8027, DRILL-8028 and possibly DRILL-8009 and
>> DRILL-7978 get merged for the next release. DRILL-7871 would be a
>> stretch goal.
>> Best,
>> — C
>>
>>> On Nov 3, 2021, at 9:21 AM, luoc <lu...@apache.org> wrote:
>>>
>>>
>>> Thanks for your support, James. Since there are no negative votes, I
>>> will recommend you as the release manager.
>>>
>>> We'll keep a light on for you.
>>>
>>>> 在 2021年11月3日，01:04，James Turton <ja...@somecomputer.xyz> 写道：
>>>>
>>>> Hi luoc
>>>>
>>>> I am willing to help the release in any capacity needed. I know
>>>> there are others who have release experience while I do not but I'm
>>>> sure it can be learned. I'll have PR #2351 done this week, it
>>>> would be nice (but not critical) to include it.
>>>>
>>>> Thanks
>>>> James
>>>>
>>>>> On 2021/11/01 16:27, luoc wrote:
>>>>>
>>>>> Hello, Drill dev and users :
>>>>>
>>>>> Since the latest 1.19, Drill master branch has collected many
>>>>> changes, bug fixed and enhanced. Drill team plan to release the
>>>>> 1.20 at the end of November 2021.
>>>>>
>>>>> We have some things to work out :
>>>>>
>>>>> 1. Are you willing to be the 1.20 release manager?
>>>>>
>>>>> 2. Is there one of the unmerged pull request that you want to
>>>>> complete?
>>>>>
>>>>> 3. Do you have a feature under development and want to include in
>>>>> 1.20?
>>>>>
>>>>> 4. Would you like to help with the test and feedback (build with
>>>>> master branch)?
>>>>>
>>>>> I hope everyone will participate in the talk and reply to these
>>>>> questions as soon as possible, thank you.
>>>>>
>>>>> -- luoc
>>>>>
>>>>>
Re: Drill 1.20 release plan
Posted by James Turton <dz...@apache.org>.
Dear dev community
Please see an update on the Jiras earmarked for 1.20 below. We have of course also closed other Jiras in the intervening period. If you are aware of any reason that one of the listed Jiras will not be ready please say so, so I can remove it. Otherwise I'll post comments to the authors asking them to aim for merging by the release cut-off date. How does a cut-off date of 10 December sound?
(* indicates a Jira not previously discussed in this thread.)
Closed:
DRILL-1282 Parquet v2 read+write
DRILL-8027 Iceberg format
Open:
DRILL-7863 Phoenix storage
DRILL-7978 Fixed width format
DRILL-7983 Get running/completed profiles from REST API (corrected from 7938 which I believe was a typo)
DRILL-8009 JDBC isValid()
* DRILL-8015 MongoDB Metastore
DRILL-8028 PDF format
The stretch goal DRILL-7871 (StoragePluginStore instance per user) has not yet reached design consensus so I propose that it should not be included in 1.20.
On 2021/11/03 15:24, Charles Givre wrote:
> Hi Luoc,
> IMHO there are a few PRs in flight that I’d like to see included in the next release. I sent them in slack, but so that they are preserved for the mailing list. I'd like to see DRILL-1282, DRILL-7938, DRILL-8027, DRILL-8028 and possibly DRILL-8009 and DRILL-7978 get merged for the next release. DRILL-7871 would be a stretch goal.
> Best,
> — C
>
>> On Nov 3, 2021, at 9:21 AM, luoc <lu...@apache.org> wrote:
>>
>>
>> Thanks for your support, James. Since there are no negative votes, I will recommend you as the release manager.
>>
>> We'll keep a light on for you.
>>
>>> 在 2021年11月3日，01:04，James Turton <ja...@somecomputer.xyz> 写道：
>>>
>>> Hi luoc
>>>
>>> I am willing to help the release in any capacity needed. I know there are others who have release experience while I do not but I'm sure it can be learned. I'll have PR #2351 done this week, it would be nice (but not critical) to include it.
>>>
>>> Thanks
>>> James
>>>
>>>> On 2021/11/01 16:27, luoc wrote:
>>>>
>>>> Hello, Drill dev and users :
>>>>
>>>> Since the latest 1.19, Drill master branch has collected many changes, bug fixed and enhanced. Drill team plan to release the 1.20 at the end of November 2021.
>>>>
>>>> We have some things to work out :
>>>>
>>>> 1. Are you willing to be the 1.20 release manager?
>>>>
>>>> 2. Is there one of the unmerged pull request that you want to complete?
>>>>
>>>> 3. Do you have a feature under development and want to include in 1.20?
>>>>
>>>> 4. Would you like to help with the test and feedback (build with master branch)?
>>>>
>>>> I hope everyone will participate in the talk and reply to these questions as soon as possible, thank you.
>>>>
>>>> -- luoc
>>>>
>>>>
Re: Drill 1.20 release plan
Posted by Charles Givre <cg...@gmail.com>.
Hi Luoc,
IMHO there are a few PRs in flight that I’d like to see included in the next release. I sent them in slack, but so that they are preserved for the mailing list. I'd like to see DRILL-1282, DRILL-7938, DRILL-8027, DRILL-8028 and possibly DRILL-8009 and DRILL-7978 get merged for the next release. DRILL-7871 would be a stretch goal.
Best,
— C
> On Nov 3, 2021, at 9:21 AM, luoc <lu...@apache.org> wrote:
>
>
> Thanks for your support, James. Since there are no negative votes, I will recommend you as the release manager.
>
> We'll keep a light on for you.
>
>> 在 2021年11月3日，01:04，James Turton <ja...@somecomputer.xyz> 写道：
>>
>> Hi luoc
>>
>> I am willing to help the release in any capacity needed. I know there are others who have release experience while I do not but I'm sure it can be learned. I'll have PR #2351 done this week, it would be nice (but not critical) to include it.
>>
>> Thanks
>> James
>>
>>> On 2021/11/01 16:27, luoc wrote:
>>>
>>> Hello, Drill dev and users :
>>>
>>> Since the latest 1.19, Drill master branch has collected many changes, bug fixed and enhanced. Drill team plan to release the 1.20 at the end of November 2021.
>>>
>>> We have some things to work out :
>>>
>>> 1. Are you willing to be the 1.20 release manager?
>>>
>>> 2. Is there one of the unmerged pull request that you want to complete?
>>>
>>> 3. Do you have a feature under development and want to include in 1.20?
>>>
>>> 4. Would you like to help with the test and feedback (build with master branch)?
>>>
>>> I hope everyone will participate in the talk and reply to these questions as soon as possible, thank you.
>>>
>>> -- luoc
>>>
>>>
>
Re: Drill 1.20 release plan
Posted by Charles Givre <cg...@gmail.com>.
Hi Luoc,
IMHO there are a few PRs in flight that I’d like to see included in the next release. I sent them in slack, but so that they are preserved for the mailing list. I'd like to see DRILL-1282, DRILL-7938, DRILL-8027, DRILL-8028 and possibly DRILL-8009 and DRILL-7978 get merged for the next release. DRILL-7871 would be a stretch goal.
Best,
— C
> On Nov 3, 2021, at 9:21 AM, luoc <lu...@apache.org> wrote:
>
>
> Thanks for your support, James. Since there are no negative votes, I will recommend you as the release manager.
>
> We'll keep a light on for you.
>
>> 在 2021年11月3日，01:04，James Turton <ja...@somecomputer.xyz> 写道：
>>
>> Hi luoc
>>
>> I am willing to help the release in any capacity needed. I know there are others who have release experience while I do not but I'm sure it can be learned. I'll have PR #2351 done this week, it would be nice (but not critical) to include it.
>>
>> Thanks
>> James
>>
>>> On 2021/11/01 16:27, luoc wrote:
>>>
>>> Hello, Drill dev and users :
>>>
>>> Since the latest 1.19, Drill master branch has collected many changes, bug fixed and enhanced. Drill team plan to release the 1.20 at the end of November 2021.
>>>
>>> We have some things to work out :
>>>
>>> 1. Are you willing to be the 1.20 release manager?
>>>
>>> 2. Is there one of the unmerged pull request that you want to complete?
>>>
>>> 3. Do you have a feature under development and want to include in 1.20?
>>>
>>> 4. Would you like to help with the test and feedback (build with master branch)?
>>>
>>> I hope everyone will participate in the talk and reply to these questions as soon as possible, thank you.
>>>
>>> -- luoc
>>>
>>>
>
Re: Drill 1.20 release plan
Posted by luoc <lu...@apache.org>.
Thanks for your support, James. Since there are no negative votes, I will recommend you as the release manager.
We'll keep a light on for you.
> 在 2021年11月3日，01:04，James Turton <ja...@somecomputer.xyz> 写道：
>
> Hi luoc
>
> I am willing to help the release in any capacity needed. I know there are others who have release experience while I do not but I'm sure it can be learned. I'll have PR #2351 done this week, it would be nice (but not critical) to include it.
>
> Thanks
> James
>
>> On 2021/11/01 16:27, luoc wrote:
>>
>> Hello, Drill dev and users :
>>
>> Since the latest 1.19, Drill master branch has collected many changes, bug fixed and enhanced. Drill team plan to release the 1.20 at the end of November 2021.
>>
>> We have some things to work out :
>>
>> 1. Are you willing to be the 1.20 release manager?
>>
>> 2. Is there one of the unmerged pull request that you want to complete?
>>
>> 3. Do you have a feature under development and want to include in 1.20?
>>
>> 4. Would you like to help with the test and feedback (build with master branch)?
>>
>> I hope everyone will participate in the talk and reply to these questions as soon as possible, thank you.
>>
>> -- luoc
>>
>>
Re: Drill 1.20 release plan
Posted by luoc <lu...@apache.org>.
Thanks for your support, James. Since there are no negative votes, I will recommend you as the release manager.
We'll keep a light on for you.
> 在 2021年11月3日，01:04，James Turton <ja...@somecomputer.xyz> 写道：
>
> Hi luoc
>
> I am willing to help the release in any capacity needed. I know there are others who have release experience while I do not but I'm sure it can be learned. I'll have PR #2351 done this week, it would be nice (but not critical) to include it.
>
> Thanks
> James
>
>> On 2021/11/01 16:27, luoc wrote:
>>
>> Hello, Drill dev and users :
>>
>> Since the latest 1.19, Drill master branch has collected many changes, bug fixed and enhanced. Drill team plan to release the 1.20 at the end of November 2021.
>>
>> We have some things to work out :
>>
>> 1. Are you willing to be the 1.20 release manager?
>>
>> 2. Is there one of the unmerged pull request that you want to complete?
>>
>> 3. Do you have a feature under development and want to include in 1.20?
>>
>> 4. Would you like to help with the test and feedback (build with master branch)?
>>
>> I hope everyone will participate in the talk and reply to these questions as soon as possible, thank you.
>>
>> -- luoc
>>
>>
Re: Drill 1.20 release plan
Posted by James Turton <ja...@somecomputer.xyz.INVALID>.
Hi luoc
I am willing to help the release in any capacity needed. I know there
are others who have release experience while I do not but I'm sure it
can be learned. I'll have PR #2351 done this week, it would be nice
(but not critical) to include it.
Thanks
James
On 2021/11/01 16:27, luoc wrote:
>
> Hello, Drill dev and users :
>
> Since the latest 1.19, Drill master branch has collected many changes, bug fixed and enhanced. Drill team plan to release the 1.20 at the end of November 2021.
>
> We have some things to work out :
>
> 1. Are you willing to be the 1.20 release manager?
>
> 2. Is there one of the unmerged pull request that you want to complete?
>
> 3. Do you have a feature under development and want to include in 1.20?
>
> 4. Would you like to help with the test and feedback (build with master branch)?
>
> I hope everyone will participate in the talk and reply to these questions as soon as possible, thank you.
>
> -- luoc
>
>