Yeah, to contribute to JIRA maintenance, it does not need a lot of codes
given my experience.
Just to share my own story:
4 years ago when I was one of contributors, I have been looking for many
other ways around to
contribute to Spark. I noticed Sean was making exceptional efforts in the
JIRA
Thanks Sean for your elaborate and valuable explanation. I will look into
it from tomorrow and will reach out if required.
Have a good day.
Regards,
Rohit Mishra
On Tue, 28 Jul 2020 at 11:20 PM, Sean Owen wrote:
> To help with JIRA, I don't think you need to know a lot about the code
>
To help with JIRA, I don't think you need to know a lot about the code
structure. I think we're talking about more basic triage, like, is it
a question that should go to the mailing list instead? is there enough
detail to understand it at all? is it tagged with a few appropriate
components, does
Hello All,
I have recently joined the Dev mailing list to help the community. Since I
am in my attempt to understand the code base before contributing, I think
looking into Jira maintenance will be a good way to help. I will start
looking into it. Do I need anyone’s approval?
In case I need any
Thanks for doing this - and I will say this is a great way for anyone
out there to contribute directly to the project. Issue trackers need
maintenance too. It's not that hard to spot basic problems with JIRAs
and request fixes, as a way to engage the reporter usefully.
I triage PRs but rarely
Hi Spark Developers
We are implementing a new TypedImperativeAggregate which will benefit from
batch to batch update or merge. And at least, in the Sort based
aggregation, we can process inputs batch to batch.
Does anyone do the same optimization?
