I have published the below report. Please let me know if you would like me
to revise it in some way.
## Description:
The mission of Apache Impala is the creation and maintenance of software
related to a high-performance distributed SQL engine
## Issues:
There are no issues requiring board attenti
The public Jenkins server (http://jenkins.impala.io) will be taken
offline for security updates tonight Feb 12th at 9pm PST. We will
send out an email again after the updates are completed.
thanks,
-Aman
I also skimmed the blocker and critical JIRAs.
I wonder if we need to recalibrate what "blocker" and "critical" mean. In
the past both have been used in Impala with the following meanings:
* Blocker -> we will not do the targeted release until this task is
completed
* Critical -> we will try reall
Do we plan to switch the default catalog implementation to the local
catalog as well?
On Wed, Jan 29, 2020 at 3:41 PM Tim Armstrong
wrote:
> We haven't generally had clear guarantees about what OS versions we're
> going to support. I ran into issues with
> https://issues.apache.org/jira/browse/I
Yes, I think changing to local catalog can be done in 4.0 branch. Based on
the feedback received here I think we can start removing the code for 3.x
catalog implementation after we fill in some of the gaps in local catalog.
We can selectively decide which ones are (eg. external data sources, HDFS
c
Sounds good to me - that approach has been successful before - i.e.
switching the default in the major version, deprecating the old one, and
then removing it some number of releases later. Although in some cases we
have been slow to remove the code, e.g. the old decimal behaviour is still
accessibl
