Re: Blogs/Designs For Apache Hive

[Ayush Saxena]

Have played a bit with this today along with Simhadri.

The page lies here: https://hive.blog.apache.org/

It is pretty simple, not very fancy, considering my Web Designing
skills(which are technically non-existent). But gives us a template to put
blogs related to hive in a single place.

As it goes always, This place belongs to all of us, please feel free to
share links to the blogs or directly raise PR to the hive-site repo to
asf-blog branch and copy the same template as on [1]

I will announce this on our Apache Hive Twitter account and let folks know
they can have their Apache Hive blogs referenced from our website.

Thanx Everyone for the help, do share blogs related to hive and lets give a
good reading experience to folks coming around :-)

-Ayush

[1] https://github.com/apache/hive-site/blob/asf-blog/index.html#L128-L139



On Wed, 7 Jun 2023 at 20:58, Denys Kuzmenko  wrote:

> Nice, tnx Ayush!
>

Re: [DISCUSS] Automatic rerunning of failed tests in Hive Pre-commit

[Denys Kuzmenko]

I’ll second the above. We already have a number of flaky tests that would go 
undetected and just increase the build time.

Re: [DISCUSS] Automatic rerunning of failed tests in Hive Pre-commit

[Stamatis Zampetakis]

Hello,

I tend to agree with Sai; if we can run on demand the failed tests
that would be a cool feature. If we just rerun everything that fails
without questions asked we may do more harm than good. Taking into
account the fact that nobody runs all tests locally before submitting
a PR (cause it is not feasible) there is a very high chance that
things go really bad in CI and rerunning will just keep wasting
resources.

Best,
Stamatis

On Thu, Jun 8, 2023 at 7:56 PM Sai Hemanth Gantasala
 wrote:
>
> Hello everyone,
>
> My personal preference is that the option to rerun *only* the failed test
> suites should be manual. The reason is, there might be frequent intentional
> test failures (failures due to our own patch) and the tests being flaky is
> less likely. So giving the option to the user to rerun the failed test
> suites wastes fewer resources if the failures are not flaky.
> If we were to automatically retry running failed test suites, then I prefer
> the value of "rerunFailingTestsCount" to be set to 1, since there is very
> less probability that the tests will be flaky in the consecutive runs.
>
> Thanks,
> Sai.
>
> On Thu, Jun 8, 2023 at 12:07 AM Ayush Saxena  wrote:
>
> > +1 from me as well to rerun the failing tests.
> > The oracle docker is also a pain, it is one of the main reasons for
> > retriggers, these retriggers wastes a lot of resources and increases the
> > time to get build results for genuine runs.
> >
> > -Ayush
> >
> > On Thu, 8 Jun 2023 at 12:31, Butao Zhang  wrote:
> >
> > > +1. I often have to rerun whole pre-commit job due to individual unstable
> > > test, ant it is too time-consuming. It would be much better if we can set
> > > maven config to retry automatically.
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Butao Zhang
> > >
> > >  Replied Message 
> > > | From | r12 t45 |
> > > | Date | 6/8/2023 14:52 |
> > > | To |  |
> > > | Subject | [DISCUSS] Automatic rerunning of failed tests in Hive
> > > Pre-commit |
> > > Hi All,
> > >
> > > It often happens that Hive unit tests fail during pre-commit which
> > requires
> > > rerunning the whole pre-commit job and creates hours of delays.
> > > What if we set Maven config to retry failed tests automatically X times?
> > > There is "rerunFailingTestsCount" property in maven-surefire-plugin which
> > > can be used for that.
> > > I would like to hear the feedback and if it is positive I could open a
> > JIRA
> > > ticket and work on it.
> > >
> > > Thanks,
> > > Dmitriy
> > >
> >