date:20170116

Re: About Apache HAWQ home page

2017-01-16 Thread Yandong Yao

+dev@hawq for broader discussion

On Tue, Jan 17, 2017 at 3:41 PM, Ed Espino  wrote:

> Probably helpful to push this to the dev list for discussion on a new
> thread.  I don't have much if any context on the current layout but other
> dev members might.
>
> I need to remind myself all the time ... we are growing a "dev community"
> ... "dev community" ... "dev community" ... "dev community".  Especially as
> you listed "who could help to make those changes"?  I believe any committer
> in the community is capable of performing this work (
> https://git-wip-us.apache.org/repos/asf?p=incubator-hawq-site.git).
>
> -=e
>
> On Mon, Jan 16, 2017 at 11:23 PM, Yandong Yao  wrote:
>
>> A few comments
>> about HAWQ home page 
>> after talked with Tim
>> who is experienced UX guy
>> :
>>
>> 1) Remove 'More...' link and corresponding section
>> 2) Move 'Doc' link to the end of the tab list
>> 3) Change 'Source' in download section to a link, instead of using a big
>> blue button.
>>
>> Who could help to make those changes?
>>
>>
>>

Apache HAWQ 2.1.0.0-incubating release status

2017-01-16 Thread Ed Espino

HAWQ Dev,

The following issues reported in Apache HAWQ 2.1.0.0-incubating RC1 have
been fixed (committed to master and 2.1.0.0-incubating release branch).
These fixes will be included in RC2.

   - NOTICE file need to be updated to reflect the right year for copyright
   (HAWQ-1267 ).
   - pom.xml need to be updated to reflect the correct version for apache
   hawq 2.1.0.0-incubating release (HAWQ-1268
   ).
   - The "make" command generates an error on CentOS 7 when --with-perl is
   run in configure. (HAWQ-1277
   ).

We have one outstanding testing (installcheck-good) investigation task
(below) impacting Mac OSX.  As soon as this is resolved satisfactorily by
the dev community, I will start the process to create RC2.

   - Investigate installcheck-good issue on Mac OSX (HAWQ-1278
    - Reported by Ming Li <
   m...@pivotal.io> and currently assigned to Ruilong Huo ).

Regards,
-=e

-- 
*Ed Espino*
*esp...@apache.org *

Re: RHEL/CentOS 7 plperl build issue when using configure with "--with-perl" option

2017-01-16 Thread Ed Espino

Thanks Hongxu for the validation.  I have submitted PR
https://github.com/apache/incubator-hawq/pull/1091 for this issue. Once
reviewed, I will include it in the Apache 2.1.0.0-incubating RC2 release.
Any volunteers to review this PR?

Thanks,
-=e

On Mon, Jan 16, 2017 at 5:55 PM, Ma Hongxu  wrote:

> I found the same problem on CentOS7, and the patch of your mentioned can
> fix it. The patch also worked well on MacOS.
>
> Thanks, ed.
>
> 在 16/01/2017 15:57, Ed Espino 写道:
> Has anyone encountered the following build error on RHEL/CentOS 7 build
> issue when using configure with "--with-perl" option?
>
> make[3]: Entering directory `/home/centos/apache-hawq-src-
> 2.1.0.0-incubating/src/pl/plperl'
> "/usr/bin/perl" ./text2macro.pl
> --strip='^(\#.*|\s*)$' plc_perlboot.pl
> plc_trusted.pl > perlchunks.h
> "/usr/bin/perl" plperl_opmask.pl plperl_opmask.h
> "/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap
> /usr/share/perl5/ExtUtils/typemap SPI.xs >SPI.c
> "/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap
> /usr/share/perl5/ExtUtils/typemap Util.xs >Util.c
> Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file
> or directory
> Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file
> or directory
> make[3]: *** [SPI.c] Error 2
> make[3]: *** Deleting file `SPI.c'
> make[3]: *** Waiting for unfinished jobs
> make[3]: *** [Util.c] Error 2
> make[3]: *** Deleting file `Util.c'
> make[3]: Leaving directory `/home/centos/apache-hawq-src-
> 2.1.0.0-incubating/src/pl/plperl'
> make[2]: *** [all] Error 1
> make[2]: Leaving directory `/home/centos/apache-hawq-src-
> 2.1.0.0-incubating/src/pl'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/centos/apache-hawq-src-
> 2.1.0.0-incubating/src'
> make: *** [all] Error 2
>
> I also have found a fix for this which was backported from PostgreSQL to
> the Greenplum DB master branch a year ago by Heikki Linnakangas<
> https://github.com/hlinnaka> (Original PostgreSQL committer Andrew
> Dunstan >):
>
> https://github.com/greenplum-db/gpdb/commit/f493756a5ac8a90ff1d5e3b84f38a1
> 53c9f80b9c#diff-97d34e5e3684082069b6c85876df9107
>
> A have added a patch (attached) to the email for review.  It corrects the
> build issue identified above. When the Apache JIRA system is back online, I
> will be creating a JIRA and corresponding pull request with this patch.
>
> -=e
> --
> Ed Espino
> esp...@apache.org
>
>
> --
> Regards,
> Hongxu.
>



-- 
*Ed Espino*
*esp...@apache.org *

[jira] [Created] (HAWQ-1277) The "make" command generates an error on CentOS 7 when --with-perl is run in configure.

2017-01-16 Thread Ed Espino (JIRA)

Ed Espino created HAWQ-1277:
---

 Summary: The "make" command generates an error on CentOS 7 when 
--with-perl is run in configure.
 Key: HAWQ-1277
 URL: https://issues.apache.org/jira/browse/HAWQ-1277
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Build
Reporter: Ed Espino
Assignee: Ed Espino
 Fix For: 2.1.0.0-incubating


The following "make" error is encountered on CentOS 7 when --with-perl is run 
in configure:

{code}
make[3]: Entering directory 
`/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl/plperl'
"/usr/bin/perl" ./text2macro.pl --strip='^(\#.*|\s*)$' 
plc_perlboot.pl plc_trusted.pl > 
perlchunks.h
"/usr/bin/perl" plperl_opmask.pl plperl_opmask.h
"/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap 
/usr/share/perl5/ExtUtils/typemap SPI.xs >SPI.c
"/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap 
/usr/share/perl5/ExtUtils/typemap Util.xs >Util.c
Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file or 
directory
Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file or 
directory
make[3]: *** [SPI.c] Error 2
make[3]: *** Deleting file `SPI.c'
make[3]: *** Waiting for unfinished jobs
make[3]: *** [Util.c] Error 2
make[3]: *** Deleting file `Util.c'
make[3]: Leaving directory 
`/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl/plperl'
make[2]: *** [all] Error 1
make[2]: Leaving directory 
`/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/centos/apache-hawq-src-2.1.0.0-incubating/src'
make: *** [all] Error 2
{code}

I also have found a fix for this which was backported from PostgreSQL to the 
Greenplum DB master branch a year ago by Heikki 
Linnakangas (Original PostgreSQL committer Andrew 
Dunstan >):

https://github.com/greenplum-db/gpdb/commit/f493756a5ac8a90ff1d5e3b84f38a153c9f80b9c#diff-97d34e5e3684082069b6c85876df9107



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: RHEL/CentOS 7 plperl build issue when using configure with "--with-perl" option

2017-01-16 Thread Ma Hongxu

I found the same problem on CentOS7, and the patch of your mentioned can fix 
it. The patch also worked well on MacOS.

Thanks, ed.

在 16/01/2017 15:57, Ed Espino 写道:
Has anyone encountered the following build error on RHEL/CentOS 7 build issue 
when using configure with "--with-perl" option?

make[3]: Entering directory 
`/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl/plperl'
"/usr/bin/perl" ./text2macro.pl --strip='^(\#.*|\s*)$' 
plc_perlboot.pl plc_trusted.pl > 
perlchunks.h
"/usr/bin/perl" plperl_opmask.pl plperl_opmask.h
"/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap 
/usr/share/perl5/ExtUtils/typemap SPI.xs >SPI.c
"/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap 
/usr/share/perl5/ExtUtils/typemap Util.xs >Util.c
Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file or 
directory
Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file or 
directory
make[3]: *** [SPI.c] Error 2
make[3]: *** Deleting file `SPI.c'
make[3]: *** Waiting for unfinished jobs
make[3]: *** [Util.c] Error 2
make[3]: *** Deleting file `Util.c'
make[3]: Leaving directory 
`/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl/plperl'
make[2]: *** [all] Error 1
make[2]: Leaving directory 
`/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/centos/apache-hawq-src-2.1.0.0-incubating/src'
make: *** [all] Error 2

I also have found a fix for this which was backported from PostgreSQL to the 
Greenplum DB master branch a year ago by Heikki 
Linnakangas (Original PostgreSQL committer Andrew 
Dunstan >):

https://github.com/greenplum-db/gpdb/commit/f493756a5ac8a90ff1d5e3b84f38a153c9f80b9c#diff-97d34e5e3684082069b6c85876df9107

A have added a patch (attached) to the email for review.  It corrects the build 
issue identified above. When the Apache JIRA system is back online, I will be 
creating a JIRA and corresponding pull request with this patch.

-=e
--
Ed Espino
esp...@apache.org


--
Regards,
Hongxu.

[GitHub] incubator-hawq-docs pull request #86: HAWQ-1263 - misc doc updates

2017-01-16 Thread lisakowen

Github user lisakowen commented on a diff in the pull request:

https://github.com/apache/incubator-hawq-docs/pull/86#discussion_r96321794
  
--- Diff: markdown/ddl/ddl-database.html.md.erb ---
@@ -2,77 +2,75 @@
 title: Creating and Managing Databases
 ---
 
-A HAWQ system is a single instance of HAWQ. There can be several separate 
HAWQ systems installed, but usually just one is selected by environment 
variable settings. See your HAWQ administrator for details.
-
-There can be multiple databases in a HAWQ system. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time â you 
cannot cross-query between databases.
+Your HAWQ deployment may have multiple databases. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time â you 
cannot cross-query between databases.
 
 ## About Template Databases 
 
-Each new database you create is based on a *template*. HAWQ provides a 
default database, *template1*. Use *template1* to connect to HAWQ for the first 
time. HAWQ uses *template1* to create databases unless you specify another 
template. Do not create any objects in *template1* unless you want those 
objects to be in every database you create.
+Each new database you create is based on a *template*. HAWQ provides a 
default database, `template1`. HAWQ uses `template1` to create databases unless 
you specify another template. Do not create any objects in `template1` unless 
you want those objects to be in every database you create.
 
-HAWQ uses two other database templates, *template0* and *postgres*, 
internally. Do not drop or modify *template0* or *postgres*. You can use 
*template0* to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you modified 
*template1*.
+HAWQ uses two other database templates internally, `template0` and 
`postgres`. Do not drop or modify `template0` or `postgres`. You can use 
`template0` to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you have modified 
`template1`.
--- End diff --

i think template0 and template1 start out the same.  you cannot modify 
template0, but you can template1.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq-docs pull request #86: HAWQ-1263 - misc doc updates

2017-01-16 Thread dyozie

Github user dyozie commented on a diff in the pull request:

https://github.com/apache/incubator-hawq-docs/pull/86#discussion_r96318754
  
--- Diff: markdown/ddl/ddl-database.html.md.erb ---
@@ -2,77 +2,75 @@
 title: Creating and Managing Databases
 ---
 
-A HAWQ system is a single instance of HAWQ. There can be several separate 
HAWQ systems installed, but usually just one is selected by environment 
variable settings. See your HAWQ administrator for details.
-
-There can be multiple databases in a HAWQ system. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time â you 
cannot cross-query between databases.
+Your HAWQ deployment may have multiple databases. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time â you 
cannot cross-query between databases.
 
 ## About Template Databases 
 
-Each new database you create is based on a *template*. HAWQ provides a 
default database, *template1*. Use *template1* to connect to HAWQ for the first 
time. HAWQ uses *template1* to create databases unless you specify another 
template. Do not create any objects in *template1* unless you want those 
objects to be in every database you create.
+Each new database you create is based on a *template*. HAWQ provides a 
default database, `template1`. HAWQ uses `template1` to create databases unless 
you specify another template. Do not create any objects in `template1` unless 
you want those objects to be in every database you create.
 
-HAWQ uses two other database templates, *template0* and *postgres*, 
internally. Do not drop or modify *template0* or *postgres*. You can use 
*template0* to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you modified 
*template1*.
+HAWQ uses two other database templates internally, `template0` and 
`postgres`. Do not drop or modify `template0` or `postgres`. You can use 
`template0` to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you have modified 
`template1`.
 
 ## Creating a Database 
 
-The `CREATE DATABASE` command creates a new database. For example:
+You must have appropriate privileges or be a HAWQ superuser to create a 
database. If you do not have the correct privileges, you cannot create a 
database. The HAWQ administrator must either grant you the necessary privileges 
or create a database for you.
+
+The [CREATE DATABASE](../reference/sql/CREATE-DATABASE.html) command 
creates a new database. For example:
 
 ``` sql
-=> CREATE DATABASE new_dbname;
+=# CREATE DATABASE ;
 ```
 
-To create a database, you must have privileges to create a database or be 
a HAWQ superuser. If you do not have the correct privileges, you cannot create 
a database. The HAWQ administrator must either give you the necessary 
privileges or to create a database for you.
-
-You can also use the client program `createdb` to create a database. For 
example, running the following command in a command line terminal connects to 
HAWQ using the provided host name and port and creates a database named 
*mydatabase*:
+You can also use the client program `createdb` to create a database. For 
example, running the following command connects to HAWQ on the host named 
`hmaster` at port `5432` and creates a database named `mydatabase`:
 
 ``` shell
-$ createdb -h masterhost -p 5432 mydatabase
+$ createdb -h hmaster -p 5432 mydatabase
 ```
 
-The host name and port must match the host name and port of the installed 
HAWQ system.
+The host name and port must match the host name and port of the HAWQ 
master node.
 
-Some objects, such as roles, are shared by all the databases in a HAWQ 
system. Other objects, such as tables that you create, are known only in the 
database in which you create them.
+Some objects, such as roles, are shared by all of the databases in a HAWQ 
deployment. Other objects, such as tables that you create, are known only to 
the database in which you create them.
 
 ### Cloning a Database 
 
-By default, a new database is created by cloning the standard system 
database template, *template1*. Any database can be used as a template when 
creating a new database, thereby providing the capability to 'clone' or copy an 
existing database and all objects and data within that database. For example:
+By default, a new database is created by cloning the

[GitHub] incubator-hawq-docs pull request #86: HAWQ-1263 - misc doc updates

2017-01-16 Thread dyozie

Github user dyozie commented on a diff in the pull request:

https://github.com/apache/incubator-hawq-docs/pull/86#discussion_r96317760
  
--- Diff: markdown/ddl/ddl-database.html.md.erb ---
@@ -2,77 +2,75 @@
 title: Creating and Managing Databases
 ---
 
-A HAWQ system is a single instance of HAWQ. There can be several separate 
HAWQ systems installed, but usually just one is selected by environment 
variable settings. See your HAWQ administrator for details.
-
-There can be multiple databases in a HAWQ system. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time â you 
cannot cross-query between databases.
+Your HAWQ deployment may have multiple databases. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time â you 
cannot cross-query between databases.
 
 ## About Template Databases 
 
-Each new database you create is based on a *template*. HAWQ provides a 
default database, *template1*. Use *template1* to connect to HAWQ for the first 
time. HAWQ uses *template1* to create databases unless you specify another 
template. Do not create any objects in *template1* unless you want those 
objects to be in every database you create.
+Each new database you create is based on a *template*. HAWQ provides a 
default database, `template1`. HAWQ uses `template1` to create databases unless 
you specify another template. Do not create any objects in `template1` unless 
you want those objects to be in every database you create.
 
-HAWQ uses two other database templates, *template0* and *postgres*, 
internally. Do not drop or modify *template0* or *postgres*. You can use 
*template0* to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you modified 
*template1*.
+HAWQ uses two other database templates internally, `template0` and 
`postgres`. Do not drop or modify `template0` or `postgres`. You can use 
`template0` to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you have modified 
`template1`.
 
 ## Creating a Database 
 
-The `CREATE DATABASE` command creates a new database. For example:
+You must have appropriate privileges or be a HAWQ superuser to create a 
database. If you do not have the correct privileges, you cannot create a 
database. The HAWQ administrator must either grant you the necessary privileges 
or create a database for you.
+
+The [CREATE DATABASE](../reference/sql/CREATE-DATABASE.html) command 
creates a new database. For example:
 
 ``` sql
-=> CREATE DATABASE new_dbname;
+=# CREATE DATABASE ;
 ```
 
-To create a database, you must have privileges to create a database or be 
a HAWQ superuser. If you do not have the correct privileges, you cannot create 
a database. The HAWQ administrator must either give you the necessary 
privileges or to create a database for you.
-
-You can also use the client program `createdb` to create a database. For 
example, running the following command in a command line terminal connects to 
HAWQ using the provided host name and port and creates a database named 
*mydatabase*:
+You can also use the client program `createdb` to create a database. For 
example, running the following command connects to HAWQ on the host named 
`hmaster` at port `5432` and creates a database named `mydatabase`:
 
 ``` shell
-$ createdb -h masterhost -p 5432 mydatabase
+$ createdb -h hmaster -p 5432 mydatabase
 ```
 
-The host name and port must match the host name and port of the installed 
HAWQ system.
+The host name and port must match the host name and port of the HAWQ 
master node.
 
-Some objects, such as roles, are shared by all the databases in a HAWQ 
system. Other objects, such as tables that you create, are known only in the 
database in which you create them.
+Some objects, such as roles, are shared by all of the databases in a HAWQ 
deployment. Other objects, such as tables that you create, are known only to 
the database in which you create them.
 
 ### Cloning a Database 
 
-By default, a new database is created by cloning the standard system 
database template, *template1*. Any database can be used as a template when 
creating a new database, thereby providing the capability to 'clone' or copy an 
existing database and all objects and data within that database. For example:
+By default, a new database is created by cloning the

[GitHub] incubator-hawq-docs pull request #86: HAWQ-1263 - misc doc updates

2017-01-16 Thread dyozie

Github user dyozie commented on a diff in the pull request:

https://github.com/apache/incubator-hawq-docs/pull/86#discussion_r96318167
  
--- Diff: markdown/ddl/ddl-database.html.md.erb ---
@@ -2,77 +2,75 @@
 title: Creating and Managing Databases
 ---
 
-A HAWQ system is a single instance of HAWQ. There can be several separate 
HAWQ systems installed, but usually just one is selected by environment 
variable settings. See your HAWQ administrator for details.
-
-There can be multiple databases in a HAWQ system. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time â you 
cannot cross-query between databases.
+Your HAWQ deployment may have multiple databases. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time â you 
cannot cross-query between databases.
 
 ## About Template Databases 
 
-Each new database you create is based on a *template*. HAWQ provides a 
default database, *template1*. Use *template1* to connect to HAWQ for the first 
time. HAWQ uses *template1* to create databases unless you specify another 
template. Do not create any objects in *template1* unless you want those 
objects to be in every database you create.
+Each new database you create is based on a *template*. HAWQ provides a 
default database, `template1`. HAWQ uses `template1` to create databases unless 
you specify another template. Do not create any objects in `template1` unless 
you want those objects to be in every database you create.
 
-HAWQ uses two other database templates, *template0* and *postgres*, 
internally. Do not drop or modify *template0* or *postgres*. You can use 
*template0* to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you modified 
*template1*.
+HAWQ uses two other database templates internally, `template0` and 
`postgres`. Do not drop or modify `template0` or `postgres`. You can use 
`template0` to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you have modified 
`template1`.
 
 ## Creating a Database 
 
-The `CREATE DATABASE` command creates a new database. For example:
+You must have appropriate privileges or be a HAWQ superuser to create a 
database. If you do not have the correct privileges, you cannot create a 
database. The HAWQ administrator must either grant you the necessary privileges 
or create a database for you.
+
+The [CREATE DATABASE](../reference/sql/CREATE-DATABASE.html) command 
creates a new database. For example:
 
 ``` sql
-=> CREATE DATABASE new_dbname;
+=# CREATE DATABASE ;
 ```
 
-To create a database, you must have privileges to create a database or be 
a HAWQ superuser. If you do not have the correct privileges, you cannot create 
a database. The HAWQ administrator must either give you the necessary 
privileges or to create a database for you.
-
-You can also use the client program `createdb` to create a database. For 
example, running the following command in a command line terminal connects to 
HAWQ using the provided host name and port and creates a database named 
*mydatabase*:
+You can also use the client program `createdb` to create a database. For 
example, running the following command connects to HAWQ on the host named 
`hmaster` at port `5432` and creates a database named `mydatabase`:
 
 ``` shell
-$ createdb -h masterhost -p 5432 mydatabase
+$ createdb -h hmaster -p 5432 mydatabase
 ```
 
-The host name and port must match the host name and port of the installed 
HAWQ system.
+The host name and port must match the host name and port of the HAWQ 
master node.
 
-Some objects, such as roles, are shared by all the databases in a HAWQ 
system. Other objects, such as tables that you create, are known only in the 
database in which you create them.
+Some objects, such as roles, are shared by all of the databases in a HAWQ 
deployment. Other objects, such as tables that you create, are known only to 
the database in which you create them.
 
 ### Cloning a Database 
 
-By default, a new database is created by cloning the standard system 
database template, *template1*. Any database can be used as a template when 
creating a new database, thereby providing the capability to 'clone' or copy an 
existing database and all objects and data within that database. For example:
+By default, a new database is created by cloning the

[GitHub] incubator-hawq-docs pull request #85: Feature/hawq-1251

2017-01-16 Thread janebeckman

Github user janebeckman closed the pull request at:

https://github.com/apache/incubator-hawq-docs/pull/85


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: HAWQ Meetup in Beijing on 1/12/2017

2017-01-16 Thread Ruilong Huo

Good idea! The events are now in desc order according to date.

Best regards,
Ruilong Huo

On Mon, Jan 16, 2017 at 3:42 PM, Yandong Yao  wrote:

> Thanks Lili!
>
> Besides, could we sort this page by DESC order so that latest news show
> firstly.
>
> On Mon, Jan 16, 2017 at 3:27 PM, Lili Ma  wrote:
>
>> Hi all,
>>
>> You can find the detailed information including the slides for this
>> meetup in this website.  Thanks!
>> https://cwiki.apache.org/confluence/display/HAWQ/Community
>>
>> Best Regards,
>> Lili
>>
>>
>> On Thu, Jan 12, 2017 at 10:42 AM, Ruilong Huo  wrote:
>>
>>> Great to have this meetup with fantastic agenda! Thanks Brain.
>>>
>>> Best regards,
>>> Ruilong Huo
>>>
>>> On Thu, Jan 12, 2017 at 10:24 AM, Brian Lu  wrote:
>>>
 Hi All,
 We will hold HAWQ Meetup in Beijing on 1/12/2017. Below is the detail
 info. Welcome to attend. We will post meetup related material after
 finishing. Thanks.

 Date: 1/12/2017, 13:30 - 16:30
 Address: Pivotal, 12/F, Tower B, Raycom InfoTech Park, No.2 Kexueyuan
 South Road, Haidian District, Beijing 100190
 Agenda:
 13:30 - 14:00Signup
 14:00 - 14:45HAWQ2.X New Features - Yanqing Wen, Pivotal HAWQ
 Senior Engineer
 14:45 - 15:30HAWQ Elasticity - Huan Zhang, Pivotal HAWQ Senior
 Engineer
 15:30 - 16:15Data Lake and HAWQ Integration - Wenbin Lu, EMC Big
 Data Senior Engineer
 16:15 - 16:30Feedback and Photo



 Best Regards,
 Brian

>>>
>>>
>>
>
>
> --
> Best Regards,
> Yandong
>

Re: About Apache HAWQ home page

Apache HAWQ 2.1.0.0-incubating release status

Re: RHEL/CentOS 7 plperl build issue when using configure with "--with-perl" option

[jira] [Created] (HAWQ-1277) The "make" command generates an error on CentOS 7 when --with-perl is run in configure.

Re: RHEL/CentOS 7 plperl build issue when using configure with "--with-perl" option

[GitHub] incubator-hawq-docs pull request #86: HAWQ-1263 - misc doc updates

[GitHub] incubator-hawq-docs pull request #86: HAWQ-1263 - misc doc updates

[GitHub] incubator-hawq-docs pull request #86: HAWQ-1263 - misc doc updates

[GitHub] incubator-hawq-docs pull request #86: HAWQ-1263 - misc doc updates

[GitHub] incubator-hawq-docs pull request #85: Feature/hawq-1251

Re: HAWQ Meetup in Beijing on 1/12/2017

11 matches

Site Navigation

Mail list logo

Footer information