[jira] [Created] (HIVE-26595) Expose failover states in replication metrics

[Harshal Patel (Jira)]

Harshal Patel created HIVE-26595:


 Summary: Expose failover states in replication metrics
 Key: HIVE-26595
 URL: https://issues.apache.org/jira/browse/HIVE-26595
 Project: Hive
  Issue Type: Improvement
Reporter: Harshal Patel


Expose the state of failover in replication metrics



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (HIVE-26594) Upgrade netty to 4.1.77 due to CVE-2022-24823

[Devaspati Krishnatri (Jira)]

Devaspati Krishnatri created HIVE-26594:
---

 Summary: Upgrade netty to 4.1.77 due to CVE-2022-24823
 Key: HIVE-26594
 URL: https://issues.apache.org/jira/browse/HIVE-26594
 Project: Hive
  Issue Type: Task
Reporter: Devaspati Krishnatri






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Proposal: Revamp Apache Hive website.

[Simhadri G]

Thanks for the feedback Stamatis !

   - I have updated the PR to include a README.md file with instructions to
   build and view the site locally after making any new changes. This will
   help us preview the changes locally before pushing the commit. (Docker is
   not required here.)

   - Github pages was used to share the new website with the community and
   it will most likely not be necessary later on.

   - Regarding the role of Github Actions(gh-pages.yml):

   - Whenever a PR is merged to the main branch, a github action is
  triggered .
  - Github action will install a hugo and build the site with the new
  changes.  Once the build is successful, HUGO then generates a
set of static
  files and these files are automatically merged to the hive-site/asf-site
  branch by github actions bot.
  - From here, to publish  hive-site/asf-site to project web site
  sub-domain (hive.apache.org),  we need to set up a configuration
  block called publish in your .asf.yaml file. (
  
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Publishingabranchtoyourprojectwebsite).

  - We will need help from apache infra - gmcdonald
   or
  Humbedooh
   to
  make sure that we have set this up correctly.

  - I agree with your suggestion to keep the changes around the revamp
   as minimal as possible and not mix the content update with the framework
   change. In this case, we can make the other changes incrementally at a
   later stage.


Thanks!
Simhadri G

On Wed, Oct 5, 2022 at 3:41 PM Stamatis Zampetakis 
wrote:

> Thanks for staying on top of this Simhadri.
>
> I will try to help reviewing the PR once I get some time.
>
> What is not yet clear to me from this discussion or by looking at the PR
> is the workflow for making a change appear on the web (
> https://hive.apache.org/). Having a README which clearly states what
> needs to be done is a must.
>
> I also think it is quite important to have instructions and possibly
> docker images for someone to be able to test how the changes look locally
> before commiting a change to the repo.
>
> Another point that needs clarification is the role of github pages. I am
> not sure why it is necessary at the moment and what exactly is the plan
> going forward. If I understand well, currently it is used to preview the
> changes but from my perspective we shouldn't need to commit something to
> the repo to understand if something breaks or not; preview should happen
> locally.
>
> I would suggest to keep the changes around the revamp as minimal as
> possible and not mix the content update with the framework change. As
> usual, smaller changes are easier to review and merge. It is definitely
> worth updating and improving the content but let's do it incrementally so
> that changes can get merged faster.
>
> The list of committers and PMC members for Hive can be found in the apache
> phonebook [1]. The list can easily get outdated so maybe we can consider
> adding links to [1] and/or github and other places instead of duplicating
> the content. Anyways, let's first deal with the revamp and discuss content
> changes later in separate JIRAs/PRs.
>
> Best,
> Stamatis
>
> [1] https://home.apache.org/phonebook.html?project=hive
>
> On Sun, Oct 2, 2022 at 2:41 AM Simhadri G  wrote:
>
>> Hello Everyone,
>>
>> I have raised the PR for the revamped Hive Website here:
>>  https://github.com/apache/hive-site/pull/2
>>
>> I kindly request if someone can help review this PR .
>>
>> Until the PR is merged, you can find the updated website here . Please
>> have a look and any feedback is most welcome :)
>> https://simhadri-g.github.io/hive-site/
>>
>> Few other things to note:
>>
>>- We will need help from someone who has write access to hive-site
>>repo to update the github workflow once PR is merged.
>>- One more important question, I came across this (
>>https://hive.apache.org/people.html ) page, while moving the .md file
>>to the new website, which lists the current pmc and committers of hive. I
>>noticed that this list is not upto date, a lot of people seem to be 
>> missing
>>from this list. May I please know where I can find the updated date list 
>> of
>>committers and PMCs which I can refer to and update the page.
>>- Lastly, I plan to add a few more sections to the homepage soon, one
>>of the sections I have in mind is to add an overview of all the apache
>>projects that use or integrate with apache hive... If there are any other
>>suggestions in addition to this please let me know.
>>
>>
>> Thanks!
>> Simhadri G
>>
>>
>>
>> On Sat, Sep 24, 2022 at 7:03 AM Simhadri G  wrote:
>>
>>> Thanks everyone,
>>>
>>>  I will begin with creating the PR and share the link in this thread
>>> soon.
>>>
>>> Thanks
>>> 

Re: Proposal: Revamp Apache Hive website.

[Stamatis Zampetakis]

Thanks for staying on top of this Simhadri.

I will try to help reviewing the PR once I get some time.

What is not yet clear to me from this discussion or by looking at the PR is
the workflow for making a change appear on the web (https://hive.apache.org/).
Having a README which clearly states what needs to be done is a must.

I also think it is quite important to have instructions and possibly docker
images for someone to be able to test how the changes look locally before
commiting a change to the repo.

Another point that needs clarification is the role of github pages. I am
not sure why it is necessary at the moment and what exactly is the plan
going forward. If I understand well, currently it is used to preview the
changes but from my perspective we shouldn't need to commit something to
the repo to understand if something breaks or not; preview should happen
locally.

I would suggest to keep the changes around the revamp as minimal as
possible and not mix the content update with the framework change. As
usual, smaller changes are easier to review and merge. It is definitely
worth updating and improving the content but let's do it incrementally so
that changes can get merged faster.

The list of committers and PMC members for Hive can be found in the apache
phonebook [1]. The list can easily get outdated so maybe we can consider
adding links to [1] and/or github and other places instead of duplicating
the content. Anyways, let's first deal with the revamp and discuss content
changes later in separate JIRAs/PRs.

Best,
Stamatis

[1] https://home.apache.org/phonebook.html?project=hive

On Sun, Oct 2, 2022 at 2:41 AM Simhadri G  wrote:

> Hello Everyone,
>
> I have raised the PR for the revamped Hive Website here:
>  https://github.com/apache/hive-site/pull/2
>
> I kindly request if someone can help review this PR .
>
> Until the PR is merged, you can find the updated website here . Please
> have a look and any feedback is most welcome :)
> https://simhadri-g.github.io/hive-site/
>
> Few other things to note:
>
>- We will need help from someone who has write access to hive-site
>repo to update the github workflow once PR is merged.
>- One more important question, I came across this (
>https://hive.apache.org/people.html ) page, while moving the .md file
>to the new website, which lists the current pmc and committers of hive. I
>noticed that this list is not upto date, a lot of people seem to be missing
>from this list. May I please know where I can find the updated date list of
>committers and PMCs which I can refer to and update the page.
>- Lastly, I plan to add a few more sections to the homepage soon, one
>of the sections I have in mind is to add an overview of all the apache
>projects that use or integrate with apache hive... If there are any other
>suggestions in addition to this please let me know.
>
>
> Thanks!
> Simhadri G
>
>
>
> On Sat, Sep 24, 2022 at 7:03 AM Simhadri G  wrote:
>
>> Thanks everyone,
>>
>>  I will begin with creating the PR and share the link in this thread soon.
>>
>> Thanks
>> Simhadri G
>>
>> On Sat, 24 Sep 2022, 04:52 Ayush Saxena,  wrote:
>>
>>> Thanx Everyone,
>>> Almost a week and we don’t seems to have any objections to start with up
>>> revamp task with hive-site repo for now.
>>>
>>> Other things as mentioned can be followed up and we can try to ask folks
>>> to establish a PMC consensus if the need be for the futher migration tasks.
>>>
>>> Simhadri, would be good to create a Jira and link the PR and drop the
>>> link here in the thread as well, so as people interested can drop
>>> suggestions regarding the design and content of the website over there, for
>>> anything else we can always come back here if we are blocked on something,
>>> or if something more needs to be done in this context.
>>>
>>> -Ayush
>>>
>>> On 21-Sep-2022, at 6:35 PM, Stamatis Zampetakis 
>>> wrote:
>>>
>>>
>>> 
>>> The javadocs are currently in svn and they can remain there for the
>>> moment. Eventually, they could be moved to a hive-site repository and for
>>> sure we don't want them in the main hive repo. I don't see an immediate
>>> need to change the place where javadocs are stored but if needed we can
>>> raise a JIRA ticket and continue the discussion there. It's not a good idea
>>> to discuss under a closed issue/PR.
>>>
>>> The hive-site repo is always gonna be the place for storing the
>>> generated website (html files etc). When you talk about moving back to the
>>> hive repo I guess you refer to the source/markdown files. The decision to
>>> change the process of publishing the website will probably require a PMC
>>> vote with lazy consensus.
>>>
>>> I agree that we can start by updating the current setup. Then we can
>>> kick off the discussion about moving the website sources to hive repo and
>>> start publishing from there. I don't know if we need to move the javadocs,
>>> so we can postpone this discussion till we hit an