[jira] [Resolved] (HAWQ-821) Inner function does not exist while invoking from outer function on mac osx
[
https://issues.apache.org/jira/browse/HAWQ-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruilong Huo resolved HAWQ-821.
--
Resolution: Not A Bug
Fix Version/s: 2.0.0
Resolved as "Not A Bug" since it is expected behaviour per investigation.
> Inner function does not exist while invoking from outer function on mac osx
> ---
>
> Key: HAWQ-821
> URL: https://issues.apache.org/jira/browse/HAWQ-821
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Query Execution
>Affects Versions: 2.0.0
>Reporter: Ruilong Huo
>Assignee: Ruilong Huo
> Fix For: 2.0.0
>
>
> In suite of function basics in new feature test framework, inner function
> does not exist while invoking from outer function on mac osx. It works on
> rhel 6.x.
>
> {noformat}
> -- 1. prepare schema and data
> DROP TABLE IF EXISTS foo;
> CREATE TABLE foo AS SELECT * FROM generate_series(1, 10) x;
> CREATE FUNCTION inner(int) RETURNS INTEGER AS 'SELECT 1' LANGUAGE SQL
> IMMUTABLE;
> CREATE FUNCTION outer(x INT) RETURNS INT AS $$
> BEGIN
> RETURN inner(x);
> END
> $$ LANGUAGE PLPGSQL;
> -- 2. run query on mac errors out with inner function does not exist
> SELECT outer(0);
> outer
> ---
> 1
> (1 row)
> SELECT outer(0) FROM foo;
> ERROR: function inner(integer) does not exist (seg2 localhost:4
> pid=30499)
> DETAIL: PL/pgSQL function "outer" line 2 at return
> -- 3. run query on rhel 6.x succeed
> SELECT outer(0);
> outer
> ---
> 1
> (1 row)
> SELECT outer(0) FROM foo;
> outer
> ---
> 1
> 1
> 1
> 1
> 1
> 1
> 1
> 1
> 1
> 1
> (10 rows)
> -- 4. clean up
> DROP FUNCTION outer(int)
> DROP FUNCTION inner(int);
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (HAWQ-821) Inner function does not exist while invoking from outer function on mac osx
[
https://issues.apache.org/jira/browse/HAWQ-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruilong Huo closed HAWQ-821.
> Inner function does not exist while invoking from outer function on mac osx
> ---
>
> Key: HAWQ-821
> URL: https://issues.apache.org/jira/browse/HAWQ-821
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Query Execution
>Affects Versions: 2.0.0
>Reporter: Ruilong Huo
>Assignee: Ruilong Huo
> Fix For: 2.0.0
>
>
> In suite of function basics in new feature test framework, inner function
> does not exist while invoking from outer function on mac osx. It works on
> rhel 6.x.
>
> {noformat}
> -- 1. prepare schema and data
> DROP TABLE IF EXISTS foo;
> CREATE TABLE foo AS SELECT * FROM generate_series(1, 10) x;
> CREATE FUNCTION inner(int) RETURNS INTEGER AS 'SELECT 1' LANGUAGE SQL
> IMMUTABLE;
> CREATE FUNCTION outer(x INT) RETURNS INT AS $$
> BEGIN
> RETURN inner(x);
> END
> $$ LANGUAGE PLPGSQL;
> -- 2. run query on mac errors out with inner function does not exist
> SELECT outer(0);
> outer
> ---
> 1
> (1 row)
> SELECT outer(0) FROM foo;
> ERROR: function inner(integer) does not exist (seg2 localhost:4
> pid=30499)
> DETAIL: PL/pgSQL function "outer" line 2 at return
> -- 3. run query on rhel 6.x succeed
> SELECT outer(0);
> outer
> ---
> 1
> (1 row)
> SELECT outer(0) FROM foo;
> outer
> ---
> 1
> 1
> 1
> 1
> 1
> 1
> 1
> 1
> 1
> 1
> (10 rows)
> -- 4. clean up
> DROP FUNCTION outer(int)
> DROP FUNCTION inner(int);
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (HAWQ-814) Enhance user-defined function by migrating create_function_1 of UDF from installcheck to new feature test framework
[ https://issues.apache.org/jira/browse/HAWQ-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruilong Huo resolved HAWQ-814. -- Resolution: Fixed Fix Version/s: 2.0.0 create_function_1 has been migrated to new feature test framework. It has also been removed from installcheck. > Enhance user-defined function by migrating create_function_1 of UDF from > installcheck to new feature test framework > --- > > Key: HAWQ-814 > URL: https://issues.apache.org/jira/browse/HAWQ-814 > Project: Apache HAWQ > Issue Type: Test > Components: Tests >Affects Versions: 2.0.0 >Reporter: Ruilong Huo >Assignee: Ruilong Huo > Fix For: 2.0.0 > > > Need to migrate create_function_1 test in installcheck-good to new feature > test framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (HAWQ-814) Enhance user-defined function by migrating create_function_1 of UDF from installcheck to new feature test framework
[ https://issues.apache.org/jira/browse/HAWQ-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruilong Huo closed HAWQ-814. > Enhance user-defined function by migrating create_function_1 of UDF from > installcheck to new feature test framework > --- > > Key: HAWQ-814 > URL: https://issues.apache.org/jira/browse/HAWQ-814 > Project: Apache HAWQ > Issue Type: Test > Components: Tests >Affects Versions: 2.0.0 >Reporter: Ruilong Huo >Assignee: Ruilong Huo > Fix For: 2.0.0 > > > Need to migrate create_function_1 test in installcheck-good to new feature > test framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-890) .gitignore files generated by python build
Paul Guo created HAWQ-890: - Summary: .gitignore files generated by python build Key: HAWQ-890 URL: https://issues.apache.org/jira/browse/HAWQ-890 Project: Apache HAWQ Issue Type: Bug Reporter: Paul Guo Assignee: Lei Chang ../../tools/bin/pythonSrc/PSI-0.3b2_gp/build/ ../../tools/bin/pythonSrc/PSI-0.3b2_gp/psi/_version.pyc ../../tools/bin/pythonSrc/lockfile-0.9.1/build/ ../../tools/bin/pythonSrc/pychecker-0.8.18/build/ ../../tools/bin/pythonSrc/pycrypto-2.0.1/build/ ../../tools/bin/pythonSrc/unittest2-0.5.1/build/ ../../tools/bin/pythonSrc/unittest2-0.5.1/unittest2/__init__.pyc ../../tools/bin/pythonSrc/unittest2-0.5.1/unittest2/case.pyc ../../tools/bin/pythonSrc/unittest2-0.5.1/unittest2/collector.pyc ../../tools/bin/pythonSrc/unittest2-0.5.1/unittest2/compatibility.pyc ../../tools/bin/pythonSrc/unittest2-0.5.1/unittest2/loader.pyc ../../tools/bin/pythonSrc/unittest2-0.5.1/unittest2/main.pyc ../../tools/bin/pythonSrc/unittest2-0.5.1/unittest2/result.pyc ../../tools/bin/pythonSrc/unittest2-0.5.1/unittest2/runner.pyc ../../tools/bin/pythonSrc/unittest2-0.5.1/unittest2/signals.pyc ../../tools/bin/pythonSrc/unittest2-0.5.1/unittest2/suite.pyc ../../tools/bin/pythonSrc/unittest2-0.5.1/unittest2/util.pyc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #768: HAWQ-888. Hack to avoid deleted files bein...
Github user paul-guo- closed the pull request at: https://github.com/apache/incubator-hawq/pull/768 --- 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. ---
[jira] [Commented] (HAWQ-888) Hack to avoid deleted files being shown in "git status" after building.
[ https://issues.apache.org/jira/browse/HAWQ-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362306#comment-15362306 ] ASF GitHub Bot commented on HAWQ-888: - Github user paul-guo- closed the pull request at: https://github.com/apache/incubator-hawq/pull/768 > Hack to avoid deleted files being shown in "git status" after building. > --- > > Key: HAWQ-888 > URL: https://issues.apache.org/jira/browse/HAWQ-888 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: Paul Guo >Assignee: Paul Guo > > After building with pgcrypto, plr, orca, the git repos will have the > following tracked files. > Changes not staged for commit: > (use "git add/rm ..." to update what will be committed) > (use "git checkout -- ..." to discard changes in working directory) > deleted:gp-xerces/git_keep_empty_directory.readme > deleted:gporca/git_keep_empty_directory.readme > deleted:gpos/git_keep_empty_directory.readme > deleted:postgres/git_keep_empty_directory.readme > deleted:../../src/pl/plr/git_keep_empty_directory.readme > Those files are just to remind developers to not write the directory (git > does not save empty directories). This is really annoying. .gitignore does > not resolve this issue. > A simple and elegant solution is: > git update-index --assume-unchanged > however followering error is seen after parallel building, > fatal: Unable to create '/data2/github/incubator-hawq/.git/index.lock': File > exists. > If no other git process is currently running, this probably means a > git process crashed in this repository earlier. Make sure no other git > process is running and remove the file manually to continue. > I do not want to waste too much time in digging into git internals, instead, > I'd try another simple solution: > - rm -f git_keep_empty_directory.readme; \ > + mv -f gporca.git_keep_empty_directory.readme ..; \ > [ ! -d .git ] && git clone $(gporca_git) . && git checkout > $(gporca_branch); \ > + mv -f ../gporca.git_keep_empty_directory.readme .; \ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-888) Hack to avoid deleted files being shown in "git status" after building.
[ https://issues.apache.org/jira/browse/HAWQ-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362313#comment-15362313 ] Paul Guo commented on HAWQ-888: --- Talked more on this. It is easier to remove those files but leave a readme to remind developers to not create/use those directories. Thus renaming the JIRA title also. > Hack to avoid deleted files being shown in "git status" after building. > --- > > Key: HAWQ-888 > URL: https://issues.apache.org/jira/browse/HAWQ-888 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: Paul Guo >Assignee: Paul Guo > > After building with pgcrypto, plr, orca, the git repos will have the > following tracked files. > Changes not staged for commit: > (use "git add/rm ..." to update what will be committed) > (use "git checkout -- ..." to discard changes in working directory) > deleted:gp-xerces/git_keep_empty_directory.readme > deleted:gporca/git_keep_empty_directory.readme > deleted:gpos/git_keep_empty_directory.readme > deleted:postgres/git_keep_empty_directory.readme > deleted:../../src/pl/plr/git_keep_empty_directory.readme > Those files are just to remind developers to not write the directory (git > does not save empty directories). This is really annoying. .gitignore does > not resolve this issue. > A simple and elegant solution is: > git update-index --assume-unchanged > however followering error is seen after parallel building, > fatal: Unable to create '/data2/github/incubator-hawq/.git/index.lock': File > exists. > If no other git process is currently running, this probably means a > git process crashed in this repository earlier. Make sure no other git > process is running and remove the file manually to continue. > I do not want to waste too much time in digging into git internals, instead, > I'd try another simple solution: > - rm -f git_keep_empty_directory.readme; \ > + mv -f gporca.git_keep_empty_directory.readme ..; \ > [ ! -d .git ] && git clone $(gporca_git) . && git checkout > $(gporca_branch); \ > + mv -f ../gporca.git_keep_empty_directory.readme .; \ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-888) Remove some dummy files which were used to keep related "empty" directories.
[ https://issues.apache.org/jira/browse/HAWQ-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Guo updated HAWQ-888: -- Summary: Remove some dummy files which were used to keep related "empty" directories. (was: Hack to avoid deleted files being shown in "git status" after building.) > Remove some dummy files which were used to keep related "empty" directories. > > > Key: HAWQ-888 > URL: https://issues.apache.org/jira/browse/HAWQ-888 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: Paul Guo >Assignee: Paul Guo > > After building with pgcrypto, plr, orca, the git repos will have the > following tracked files. > Changes not staged for commit: > (use "git add/rm ..." to update what will be committed) > (use "git checkout -- ..." to discard changes in working directory) > deleted:gp-xerces/git_keep_empty_directory.readme > deleted:gporca/git_keep_empty_directory.readme > deleted:gpos/git_keep_empty_directory.readme > deleted:postgres/git_keep_empty_directory.readme > deleted:../../src/pl/plr/git_keep_empty_directory.readme > Those files are just to remind developers to not write the directory (git > does not save empty directories). This is really annoying. .gitignore does > not resolve this issue. > A simple and elegant solution is: > git update-index --assume-unchanged > however followering error is seen after parallel building, > fatal: Unable to create '/data2/github/incubator-hawq/.git/index.lock': File > exists. > If no other git process is currently running, this probably means a > git process crashed in this repository earlier. Make sure no other git > process is running and remove the file manually to continue. > I do not want to waste too much time in digging into git internals, instead, > I'd try another simple solution: > - rm -f git_keep_empty_directory.readme; \ > + mv -f gporca.git_keep_empty_directory.readme ..; \ > [ ! -d .git ] && git clone $(gporca_git) . && git checkout > $(gporca_branch); \ > + mv -f ../gporca.git_keep_empty_directory.readme .; \ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #773: HAWQ-888. Remove some dummy files which we...
GitHub user paul-guo- opened a pull request: https://github.com/apache/incubator-hawq/pull/773 HAWQ-888. Remove some dummy files which were used to keep related "em⦠â¦pty" directories. You can merge this pull request into a Git repository by running: $ git pull https://github.com/paul-guo-/incubator-hawq make Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/773.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #773 commit 4eda5a6f127ae65f753a8d4f217ef456cad01a6e Author: Paul Guo Date: 2016-07-05T10:16:17Z HAWQ-888. Remove some dummy files which were used to keep related "empty" directories. --- 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. ---
[jira] [Commented] (HAWQ-888) Remove some dummy files which were used to keep related "empty" directories.
[ https://issues.apache.org/jira/browse/HAWQ-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362329#comment-15362329 ] ASF GitHub Bot commented on HAWQ-888: - GitHub user paul-guo- opened a pull request: https://github.com/apache/incubator-hawq/pull/773 HAWQ-888. Remove some dummy files which were used to keep related "em… …pty" directories. You can merge this pull request into a Git repository by running: $ git pull https://github.com/paul-guo-/incubator-hawq make Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/773.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #773 commit 4eda5a6f127ae65f753a8d4f217ef456cad01a6e Author: Paul Guo Date: 2016-07-05T10:16:17Z HAWQ-888. Remove some dummy files which were used to keep related "empty" directories. > Remove some dummy files which were used to keep related "empty" directories. > > > Key: HAWQ-888 > URL: https://issues.apache.org/jira/browse/HAWQ-888 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: Paul Guo >Assignee: Paul Guo > > After building with pgcrypto, plr, orca, the git repos will have the > following tracked files. > Changes not staged for commit: > (use "git add/rm ..." to update what will be committed) > (use "git checkout -- ..." to discard changes in working directory) > deleted:gp-xerces/git_keep_empty_directory.readme > deleted:gporca/git_keep_empty_directory.readme > deleted:gpos/git_keep_empty_directory.readme > deleted:postgres/git_keep_empty_directory.readme > deleted:../../src/pl/plr/git_keep_empty_directory.readme > Those files are just to remind developers to not write the directory (git > does not save empty directories). This is really annoying. .gitignore does > not resolve this issue. > A simple and elegant solution is: > git update-index --assume-unchanged > however followering error is seen after parallel building, > fatal: Unable to create '/data2/github/incubator-hawq/.git/index.lock': File > exists. > If no other git process is currently running, this probably means a > git process crashed in this repository earlier. Make sure no other git > process is running and remove the file manually to continue. > I do not want to waste too much time in digging into git internals, instead, > I'd try another simple solution: > - rm -f git_keep_empty_directory.readme; \ > + mv -f gporca.git_keep_empty_directory.readme ..; \ > [ ! -d .git ] && git clone $(gporca_git) . && git checkout > $(gporca_branch); \ > + mv -f ../gporca.git_keep_empty_directory.readme .; \ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #773: HAWQ-888. Remove some dummy files which were used...
Github user radarwave commented on the issue: https://github.com/apache/incubator-hawq/pull/773 I think this is better than the previous hack, usually users won't create the directories by themselves. +1 --- 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. ---
[jira] [Commented] (HAWQ-888) Remove some dummy files which were used to keep related "empty" directories.
[ https://issues.apache.org/jira/browse/HAWQ-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362456#comment-15362456 ] ASF GitHub Bot commented on HAWQ-888: - Github user radarwave commented on the issue: https://github.com/apache/incubator-hawq/pull/773 I think this is better than the previous hack, usually users won't create the directories by themselves. +1 > Remove some dummy files which were used to keep related "empty" directories. > > > Key: HAWQ-888 > URL: https://issues.apache.org/jira/browse/HAWQ-888 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: Paul Guo >Assignee: Paul Guo > > After building with pgcrypto, plr, orca, the git repos will have the > following tracked files. > Changes not staged for commit: > (use "git add/rm ..." to update what will be committed) > (use "git checkout -- ..." to discard changes in working directory) > deleted:gp-xerces/git_keep_empty_directory.readme > deleted:gporca/git_keep_empty_directory.readme > deleted:gpos/git_keep_empty_directory.readme > deleted:postgres/git_keep_empty_directory.readme > deleted:../../src/pl/plr/git_keep_empty_directory.readme > Those files are just to remind developers to not write the directory (git > does not save empty directories). This is really annoying. .gitignore does > not resolve this issue. > A simple and elegant solution is: > git update-index --assume-unchanged > however followering error is seen after parallel building, > fatal: Unable to create '/data2/github/incubator-hawq/.git/index.lock': File > exists. > If no other git process is currently running, this probably means a > git process crashed in this repository earlier. Make sure no other git > process is running and remove the file manually to continue. > I do not want to waste too much time in digging into git internals, instead, > I'd try another simple solution: > - rm -f git_keep_empty_directory.readme; \ > + mv -f gporca.git_keep_empty_directory.readme ..; \ > [ ! -d .git ] && git clone $(gporca_git) . && git checkout > $(gporca_branch); \ > + mv -f ../gporca.git_keep_empty_directory.readme .; \ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-891) Refine libyarn source codes
[ https://issues.apache.org/jira/browse/HAWQ-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Wen reassigned HAWQ-891: Assignee: Lin Wen (was: Lei Chang) > Refine libyarn source codes > --- > > Key: HAWQ-891 > URL: https://issues.apache.org/jira/browse/HAWQ-891 > Project: Apache HAWQ > Issue Type: Bug > Components: libyarn >Reporter: Lin Wen >Assignee: Lin Wen > > Some parts of libyarn source codes need to be refined. > 1. some definition of exception in exception.h are useless; e.g. > FileAlreadyExistsException > 2. some interface need to be changed. e.g. constructor of class > LibYarnNodeInfo, use C++ string instead of char*; > 3. fix misspelling, e.g. "contaier" should be "container" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-891) Refine libyarn source codes
Lin Wen created HAWQ-891: Summary: Refine libyarn source codes Key: HAWQ-891 URL: https://issues.apache.org/jira/browse/HAWQ-891 Project: Apache HAWQ Issue Type: Bug Components: libyarn Reporter: Lin Wen Assignee: Lei Chang Some parts of libyarn source codes need to be refined. 1. some definition of exception in exception.h are useless; e.g. FileAlreadyExistsException 2. some interface need to be changed. e.g. constructor of class LibYarnNodeInfo, use C++ string instead of char*; 3. fix misspelling, e.g. "contaier" should be "container" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #773: HAWQ-888. Remove some dummy files which were used...
Github user xunzhang commented on the issue: https://github.com/apache/incubator-hawq/pull/773 Could you add the clone info more specifically? For example, I tried your branch under my Mac and got error below, but I could not even know which repo is failed during cloning. ``` Cloning into '.'... remote: Counting objects: 589045, done. remote: Compressing objects: 100% (73/73), done. error: RPC failed; curl 56 SSLRead() return error -36 251.00 KiB/s fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed fatal: Could not parse object 'ca59dfa6f727fe3bf3a01904ec30e87f7fa5a67e'. Now fetch from upstream and try again From https://github.com/paul-guo-/incubator-hawq * branchmaster -> FETCH_HEAD fatal: Could not parse object 'ca59dfa6f727fe3bf3a01904ec30e87f7fa5a67e'. make[1]: *** [pgcrypto_prepare] Error 2 make: *** [all] Error 2 ``` --- 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. ---
[jira] [Commented] (HAWQ-888) Remove some dummy files which were used to keep related "empty" directories.
[ https://issues.apache.org/jira/browse/HAWQ-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362595#comment-15362595 ] ASF GitHub Bot commented on HAWQ-888: - Github user xunzhang commented on the issue: https://github.com/apache/incubator-hawq/pull/773 Could you add the clone info more specifically? For example, I tried your branch under my Mac and got error below, but I could not even know which repo is failed during cloning. ``` Cloning into '.'... remote: Counting objects: 589045, done. remote: Compressing objects: 100% (73/73), done. error: RPC failed; curl 56 SSLRead() return error -36 251.00 KiB/s fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed fatal: Could not parse object 'ca59dfa6f727fe3bf3a01904ec30e87f7fa5a67e'. Now fetch from upstream and try again From https://github.com/paul-guo-/incubator-hawq * branchmaster -> FETCH_HEAD fatal: Could not parse object 'ca59dfa6f727fe3bf3a01904ec30e87f7fa5a67e'. make[1]: *** [pgcrypto_prepare] Error 2 make: *** [all] Error 2 ``` > Remove some dummy files which were used to keep related "empty" directories. > > > Key: HAWQ-888 > URL: https://issues.apache.org/jira/browse/HAWQ-888 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: Paul Guo >Assignee: Paul Guo > > After building with pgcrypto, plr, orca, the git repos will have the > following tracked files. > Changes not staged for commit: > (use "git add/rm ..." to update what will be committed) > (use "git checkout -- ..." to discard changes in working directory) > deleted:gp-xerces/git_keep_empty_directory.readme > deleted:gporca/git_keep_empty_directory.readme > deleted:gpos/git_keep_empty_directory.readme > deleted:postgres/git_keep_empty_directory.readme > deleted:../../src/pl/plr/git_keep_empty_directory.readme > Those files are just to remind developers to not write the directory (git > does not save empty directories). This is really annoying. .gitignore does > not resolve this issue. > A simple and elegant solution is: > git update-index --assume-unchanged > however followering error is seen after parallel building, > fatal: Unable to create '/data2/github/incubator-hawq/.git/index.lock': File > exists. > If no other git process is currently running, this probably means a > git process crashed in this repository earlier. Make sure no other git > process is running and remove the file manually to continue. > I do not want to waste too much time in digging into git internals, instead, > I'd try another simple solution: > - rm -f git_keep_empty_directory.readme; \ > + mv -f gporca.git_keep_empty_directory.readme ..; \ > [ ! -d .git ] && git clone $(gporca_git) . && git checkout > $(gporca_branch); \ > + mv -f ../gporca.git_keep_empty_directory.readme .; \ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (HAWQ-867) Replace the git-submobule mechanism with git-clone
[ https://issues.apache.org/jira/browse/HAWQ-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goden Yao reopened HAWQ-867: reopen to edit release info > Replace the git-submobule mechanism with git-clone > -- > > Key: HAWQ-867 > URL: https://issues.apache.org/jira/browse/HAWQ-867 > Project: Apache HAWQ > Issue Type: Bug >Reporter: Paul Guo >Assignee: Paul Guo > Fix For: 2.0.0-incubating > > > Currently some features/extensions (e.g. pycrytpo, gporca, etc) are embedded > into hawq code via the git submodule mechanism which is similar to a link. In > hawq git repo, during hawq build, it will download the submodule repos and > build those functionality, however if we decide to generate a source tarball > which is independent on the git repo, this will be an issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-867) Replace the git-submobule mechanism with git-clone
[ https://issues.apache.org/jira/browse/HAWQ-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goden Yao updated HAWQ-867: --- Fix Version/s: 2.0.0-incubating > Replace the git-submobule mechanism with git-clone > -- > > Key: HAWQ-867 > URL: https://issues.apache.org/jira/browse/HAWQ-867 > Project: Apache HAWQ > Issue Type: Bug >Reporter: Paul Guo >Assignee: Paul Guo > Fix For: 2.0.0-incubating > > > Currently some features/extensions (e.g. pycrytpo, gporca, etc) are embedded > into hawq code via the git submodule mechanism which is similar to a link. In > hawq git repo, during hawq build, it will download the submodule repos and > build those functionality, however if we decide to generate a source tarball > which is independent on the git repo, this will be an issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-783) Remove quicklz in medadata
[ https://issues.apache.org/jira/browse/HAWQ-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goden Yao updated HAWQ-783: --- Fix Version/s: (was: 2.0.0-incubating) 2.1.0 > Remove quicklz in medadata > -- > > Key: HAWQ-783 > URL: https://issues.apache.org/jira/browse/HAWQ-783 > Project: Apache HAWQ > Issue Type: Bug > Components: Storage >Reporter: Paul Guo >Assignee: Lei Chang > Fix For: 2.1.0 > > > This is the rest work of complete quicklz removal, beside HAWQ-780 (Remove > quicklz compression related code but keep related meta data in short term). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-886) Support PXF filter push down for ORC
[ https://issues.apache.org/jira/browse/HAWQ-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shivram Mani reassigned HAWQ-886: - Assignee: Shivram Mani (was: Goden Yao) > Support PXF filter push down for ORC > > > Key: HAWQ-886 > URL: https://issues.apache.org/jira/browse/HAWQ-886 > Project: Apache HAWQ > Issue Type: New Feature > Components: PXF >Reporter: Shivram Mani >Assignee: Shivram Mani > > Currently PXF via the Hive profile doesn’t pass any of the filter information > down while accessing ORC files. The only filter that is possible right now is > at the level of partition and is generically done for all Hive tables. > ORC reader BuilderOptions includes the ability to define SearchArgument which > contains the filter information to be push down to the reader. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-886) Support PXF filter push down for ORC
[ https://issues.apache.org/jira/browse/HAWQ-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goden Yao updated HAWQ-886: --- Fix Version/s: 2.1.0 > Support PXF filter push down for ORC > > > Key: HAWQ-886 > URL: https://issues.apache.org/jira/browse/HAWQ-886 > Project: Apache HAWQ > Issue Type: New Feature > Components: PXF >Reporter: Shivram Mani >Assignee: Shivram Mani > Fix For: 2.1.0 > > > Currently PXF via the Hive profile doesn’t pass any of the filter information > down while accessing ORC files. The only filter that is possible right now is > at the level of partition and is generically done for all Hive tables. > ORC reader BuilderOptions includes the ability to define SearchArgument which > contains the filter information to be push down to the reader. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-886) Support PXF filter push down for ORC
[ https://issues.apache.org/jira/browse/HAWQ-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shivram Mani updated HAWQ-886: -- Description: Currently PXF via the Hive profile doesn’t pass any of the filter information down while accessing ORC files. The only filter that is possible right now is at the level of partition and is generically done for all Hive tables. ORC internally contains file level, stripe level and row level statistics including information such as min,max values etc. For more information refer to https://orc.apache.org/docs/indexes.html The proposal here is to possibly introduce a new profile optimized for ORC files and to leverage these stats to improve the performance of HAWQ queries with predicates. was: Currently PXF via the Hive profile doesn’t pass any of the filter information down while accessing ORC files. The only filter that is possible right now is at the level of partition and is generically done for all Hive tables. ORC reader BuilderOptions includes the ability to define SearchArgument which contains the filter information to be push down to the reader. > Support PXF filter push down for ORC > > > Key: HAWQ-886 > URL: https://issues.apache.org/jira/browse/HAWQ-886 > Project: Apache HAWQ > Issue Type: New Feature > Components: PXF >Reporter: Shivram Mani >Assignee: Shivram Mani > Fix For: 2.1.0 > > > Currently PXF via the Hive profile doesn’t pass any of the filter information > down while accessing ORC files. The only filter that is possible right now is > at the level of partition and is generically done for all Hive tables. > ORC internally contains file level, stripe level and row level statistics > including information such as min,max values etc. For more information refer > to https://orc.apache.org/docs/indexes.html > The proposal here is to possibly introduce a new profile optimized for ORC > files and to leverage these stats to improve the performance of HAWQ queries > with predicates. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-886) Support PXF filter push down for ORC
[ https://issues.apache.org/jira/browse/HAWQ-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362999#comment-15362999 ] Shivram Mani commented on HAWQ-886: --- Based on an initial performance evaluation on Reading ORC files with features turned on/off Data ~ 50 rows 6 columns with primitive data types Read using naive row based reader ~ 1500ms Read using Vectorizedbatch reader (default 1024 batch size) ~ 1000ms Read with filter (7500 rows) ~ 750ms Read without filter with column projection ~ 850ms Read with filter with column projection ~ 600ms Over all we can achieve roughly a 60% speedup over a rather small dataset. > Support PXF filter push down for ORC > > > Key: HAWQ-886 > URL: https://issues.apache.org/jira/browse/HAWQ-886 > Project: Apache HAWQ > Issue Type: New Feature > Components: PXF >Reporter: Shivram Mani >Assignee: Shivram Mani > Fix For: 2.1.0 > > > Currently PXF via the Hive profile doesn’t pass any of the filter information > down while accessing ORC files. The only filter that is possible right now is > at the level of partition and is generically done for all Hive tables. > ORC internally contains file level, stripe level and row level statistics > including information such as min,max values etc. For more information refer > to https://orc.apache.org/docs/indexes.html > The proposal here is to possibly introduce a new profile optimized for ORC > files and to leverage these stats to improve the performance of HAWQ queries > with predicates. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-886) Support PXF filter push down for ORC
[ https://issues.apache.org/jira/browse/HAWQ-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shivram Mani updated HAWQ-886: -- Description: Currently HAWQ when reading ORC files via PXF (using the default Hive profile) doesn’t pass any of the filter information down. The only filter that is possible right now is at the level of partition and is generically done for all Hive tables. ORC internally contains file level, stripe level and row level statistics including information such as min,max values etc. For more information refer to https://orc.apache.org/docs/indexes.html The proposal here is to possibly introduce a new profile optimized for ORC files and to leverage these stats to improve the performance of HAWQ queries with predicates. We will also use the Vectorized approach while reading as opposed to the existing reader which is row based on more expensive. was: Currently PXF via the Hive profile doesn’t pass any of the filter information down while accessing ORC files. The only filter that is possible right now is at the level of partition and is generically done for all Hive tables. ORC internally contains file level, stripe level and row level statistics including information such as min,max values etc. For more information refer to https://orc.apache.org/docs/indexes.html The proposal here is to possibly introduce a new profile optimized for ORC files and to leverage these stats to improve the performance of HAWQ queries with predicates. > Support PXF filter push down for ORC > > > Key: HAWQ-886 > URL: https://issues.apache.org/jira/browse/HAWQ-886 > Project: Apache HAWQ > Issue Type: New Feature > Components: PXF >Reporter: Shivram Mani >Assignee: Shivram Mani > Fix For: 2.1.0 > > > Currently HAWQ when reading ORC files via PXF (using the default Hive > profile) doesn’t pass any of the filter information down. The only filter > that is possible right now is at the level of partition and is generically > done for all Hive tables. > ORC internally contains file level, stripe level and row level statistics > including information such as min,max values etc. For more information refer > to https://orc.apache.org/docs/indexes.html > The proposal here is to possibly introduce a new profile optimized for ORC > files and to leverage these stats to improve the performance of HAWQ queries > with predicates. We will also use the Vectorized approach while reading as > opposed to the existing reader which is row based on more expensive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-886) Support PXF filter push down for ORC
[ https://issues.apache.org/jira/browse/HAWQ-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shivram Mani updated HAWQ-886: -- Description: Currently HAWQ when reading ORC files via PXF (using the default Hive profile) doesn’t push down any of the filter information down to the underlying ORC reader. The only filter that is possible right now is at the level of partition and is generically done for all Hive tables. ORC internally contains file level, stripe level and row level statistics including information such as min,max values etc. For more information refer to https://orc.apache.org/docs/indexes.html The proposal here is to introduce a new PXF profile optimized for ORC files which leverages these stats to improve the performance of HAWQ queries with predicates. We will also use the Vectorized approach while reading as opposed to the existing reader which is row based on more expensive. was: Currently HAWQ when reading ORC files via PXF (using the default Hive profile) doesn’t pass any of the filter information down. The only filter that is possible right now is at the level of partition and is generically done for all Hive tables. ORC internally contains file level, stripe level and row level statistics including information such as min,max values etc. For more information refer to https://orc.apache.org/docs/indexes.html The proposal here is to possibly introduce a new profile optimized for ORC files and to leverage these stats to improve the performance of HAWQ queries with predicates. We will also use the Vectorized approach while reading as opposed to the existing reader which is row based on more expensive. > Support PXF filter push down for ORC > > > Key: HAWQ-886 > URL: https://issues.apache.org/jira/browse/HAWQ-886 > Project: Apache HAWQ > Issue Type: New Feature > Components: PXF >Reporter: Shivram Mani >Assignee: Shivram Mani > Fix For: 2.1.0 > > > Currently HAWQ when reading ORC files via PXF (using the default Hive > profile) doesn’t push down any of the filter information down to the > underlying ORC reader. The only filter that is possible right now is at the > level of partition and is generically done for all Hive tables. > ORC internally contains file level, stripe level and row level statistics > including information such as min,max values etc. For more information refer > to https://orc.apache.org/docs/indexes.html > The proposal here is to introduce a new PXF profile optimized for ORC files > which leverages these stats to improve the performance of HAWQ queries with > predicates. We will also use the Vectorized approach while reading as opposed > to the existing reader which is row based on more expensive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (HAWQ-886) Support PXF filter push down for ORC
[ https://issues.apache.org/jira/browse/HAWQ-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362999#comment-15362999 ] Goden Yao edited comment on HAWQ-886 at 7/5/16 7:01 PM: Based on an initial performance evaluation on Reading ORC files with features turned on/off Data ~ 50 rows 6 columns with primitive data types Read using native row based reader ~ 1500ms Read using Vectorizedbatch reader (default 1024 batch size) ~ 1000ms Read with filter (7500 rows) ~ 750ms Read without filter with column projection ~ 850ms Read with filter with column projection ~ 600ms Over all we can achieve roughly a 60% speedup over a rather small dataset. was (Author: shivram): Based on an initial performance evaluation on Reading ORC files with features turned on/off Data ~ 50 rows 6 columns with primitive data types Read using naive row based reader ~ 1500ms Read using Vectorizedbatch reader (default 1024 batch size) ~ 1000ms Read with filter (7500 rows) ~ 750ms Read without filter with column projection ~ 850ms Read with filter with column projection ~ 600ms Over all we can achieve roughly a 60% speedup over a rather small dataset. > Support PXF filter push down for ORC > > > Key: HAWQ-886 > URL: https://issues.apache.org/jira/browse/HAWQ-886 > Project: Apache HAWQ > Issue Type: New Feature > Components: PXF >Reporter: Shivram Mani >Assignee: Shivram Mani > Fix For: 2.1.0 > > > Currently HAWQ when reading ORC files via PXF (using the default Hive > profile) doesn’t push down any of the filter information down to the > underlying ORC reader. The only filter that is possible right now is at the > level of partition and is generically done for all Hive tables. > ORC internally contains file level, stripe level and row level statistics > including information such as min,max values etc. For more information refer > to https://orc.apache.org/docs/indexes.html > The proposal here is to introduce a new PXF profile optimized for ORC files > which leverages these stats to improve the performance of HAWQ queries with > predicates. We will also use the Vectorized approach while reading as opposed > to the existing reader which is row based on more expensive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-886) Support PXF filter push down for ORC
[ https://issues.apache.org/jira/browse/HAWQ-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shivram Mani updated HAWQ-886: -- Description: Currently HAWQ when reading ORC files via PXF (using the default Hive profile) doesn’t push down any of the filter information down to the underlying ORC reader. The only filter that is possible right now is at the level of partition and is generically done for all Hive tables. ORC internally contains file level, stripe level and row level statistics including information such as min,max values etc. For more information refer to https://orc.apache.org/docs/indexes.html The proposal here is to introduce a new PXF profile optimized for ORC files which leverages these stats to improve the performance of HAWQ queries with predicates. We will also use the Vectorized approach (VectorizedRowBatch) while reading along with SearchArgument to build the filter as opposed to the existing expensive reader which is row based. was: Currently HAWQ when reading ORC files via PXF (using the default Hive profile) doesn’t push down any of the filter information down to the underlying ORC reader. The only filter that is possible right now is at the level of partition and is generically done for all Hive tables. ORC internally contains file level, stripe level and row level statistics including information such as min,max values etc. For more information refer to https://orc.apache.org/docs/indexes.html The proposal here is to introduce a new PXF profile optimized for ORC files which leverages these stats to improve the performance of HAWQ queries with predicates. We will also use the Vectorized approach while reading as opposed to the existing reader which is row based on more expensive. > Support PXF filter push down for ORC > > > Key: HAWQ-886 > URL: https://issues.apache.org/jira/browse/HAWQ-886 > Project: Apache HAWQ > Issue Type: New Feature > Components: PXF >Reporter: Shivram Mani >Assignee: Shivram Mani > Fix For: 2.1.0 > > > Currently HAWQ when reading ORC files via PXF (using the default Hive > profile) doesn’t push down any of the filter information down to the > underlying ORC reader. The only filter that is possible right now is at the > level of partition and is generically done for all Hive tables. > ORC internally contains file level, stripe level and row level statistics > including information such as min,max values etc. For more information refer > to https://orc.apache.org/docs/indexes.html > The proposal here is to introduce a new PXF profile optimized for ORC files > which leverages these stats to improve the performance of HAWQ queries with > predicates. We will also use the Vectorized approach (VectorizedRowBatch) > while reading along with SearchArgument to build the filter as opposed to the > existing expensive reader which is row based. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-892) Need "incubating" in Apache HAWQ release
[ https://issues.apache.org/jira/browse/HAWQ-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goden Yao updated HAWQ-892: --- Issue Type: Bug (was: Task) > Need "incubating" in Apache HAWQ release > > > Key: HAWQ-892 > URL: https://issues.apache.org/jira/browse/HAWQ-892 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: Goden Yao >Assignee: Lei Chang > Fix For: 2.0.0-incubating > > > our version file in 2.0.0-incubating branch should be "2.0.0-incubating". > Master should be "2.0.1-incubating" (or whatever the next version) > Hawq commandline --version should also show "incubating" in the version > number before we graduate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-892) Need "incubating" in Apache HAWQ release
[ https://issues.apache.org/jira/browse/HAWQ-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goden Yao updated HAWQ-892: --- Fix Version/s: 2.0.0-incubating > Need "incubating" in Apache HAWQ release > > > Key: HAWQ-892 > URL: https://issues.apache.org/jira/browse/HAWQ-892 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: Goden Yao >Assignee: Lei Chang > Fix For: 2.0.0-incubating > > > our version file in 2.0.0-incubating branch should be "2.0.0-incubating". > Master should be "2.0.1-incubating" (or whatever the next version) > Hawq commandline --version should also show "incubating" in the version > number before we graduate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-892) Need "incubating" in Apache HAWQ release
Goden Yao created HAWQ-892: -- Summary: Need "incubating" in Apache HAWQ release Key: HAWQ-892 URL: https://issues.apache.org/jira/browse/HAWQ-892 Project: Apache HAWQ Issue Type: Task Components: Build Reporter: Goden Yao Assignee: Lei Chang our version file in 2.0.0-incubating branch should be "2.0.0-incubating". Master should be "2.0.1-incubating" (or whatever the next version) Hawq commandline --version should also show "incubating" in the version number before we graduate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (HAWQ-867) Replace the git-submobule mechanism with git-clone
[ https://issues.apache.org/jira/browse/HAWQ-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362814#comment-15362814 ] Goden Yao edited comment on HAWQ-867 at 7/6/16 1:04 AM: reopen to edit release info. We need to port this to 2.0.0-incubating branch if it's a blocker. was (Author: godenyao): reopen to edit release info > Replace the git-submobule mechanism with git-clone > -- > > Key: HAWQ-867 > URL: https://issues.apache.org/jira/browse/HAWQ-867 > Project: Apache HAWQ > Issue Type: Bug >Reporter: Paul Guo >Assignee: Paul Guo > Fix For: 2.0.0-incubating > > > Currently some features/extensions (e.g. pycrytpo, gporca, etc) are embedded > into hawq code via the git submodule mechanism which is similar to a link. In > hawq git repo, during hawq build, it will download the submodule repos and > build those functionality, however if we decide to generate a source tarball > which is independent on the git repo, this will be an issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #773: HAWQ-888. Remove some dummy files which were used...
Github user paul-guo- commented on the issue: https://github.com/apache/incubator-hawq/pull/773 @xunzhang, make fails because "git clone" fails, probably because of network issue or something else. This is not a makefile bug. You can try run make again. By the way, the build log includes the git command line (thus includes repo info). Just check the log before "Cloning into". --- 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. ---
[jira] [Commented] (HAWQ-888) Remove some dummy files which were used to keep related "empty" directories.
[ https://issues.apache.org/jira/browse/HAWQ-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363571#comment-15363571 ] ASF GitHub Bot commented on HAWQ-888: - Github user paul-guo- commented on the issue: https://github.com/apache/incubator-hawq/pull/773 @xunzhang, make fails because "git clone" fails, probably because of network issue or something else. This is not a makefile bug. You can try run make again. By the way, the build log includes the git command line (thus includes repo info). Just check the log before "Cloning into". > Remove some dummy files which were used to keep related "empty" directories. > > > Key: HAWQ-888 > URL: https://issues.apache.org/jira/browse/HAWQ-888 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: Paul Guo >Assignee: Paul Guo > > After building with pgcrypto, plr, orca, the git repos will have the > following tracked files. > Changes not staged for commit: > (use "git add/rm ..." to update what will be committed) > (use "git checkout -- ..." to discard changes in working directory) > deleted:gp-xerces/git_keep_empty_directory.readme > deleted:gporca/git_keep_empty_directory.readme > deleted:gpos/git_keep_empty_directory.readme > deleted:postgres/git_keep_empty_directory.readme > deleted:../../src/pl/plr/git_keep_empty_directory.readme > Those files are just to remind developers to not write the directory (git > does not save empty directories). This is really annoying. .gitignore does > not resolve this issue. > A simple and elegant solution is: > git update-index --assume-unchanged > however followering error is seen after parallel building, > fatal: Unable to create '/data2/github/incubator-hawq/.git/index.lock': File > exists. > If no other git process is currently running, this probably means a > git process crashed in this repository earlier. Make sure no other git > process is running and remove the file manually to continue. > I do not want to waste too much time in digging into git internals, instead, > I'd try another simple solution: > - rm -f git_keep_empty_directory.readme; \ > + mv -f gporca.git_keep_empty_directory.readme ..; \ > [ ! -d .git ] && git clone $(gporca_git) . && git checkout > $(gporca_branch); \ > + mv -f ../gporca.git_keep_empty_directory.readme .; \ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #774: HAWQ-891. Refine libyarn codes
GitHub user linwen opened a pull request: https://github.com/apache/incubator-hawq/pull/774 HAWQ-891. Refine libyarn codes Please review, thanks! You can merge this pull request into a Git repository by running: $ git pull https://github.com/linwen/incubator-hawq hawq-891 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/774.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #774 commit 383818c280f3b4787c726920105585c09bd7630f Author: Wen Lin Date: 2016-07-06T01:33:56Z HAWQ-891. Refine libyarn codes --- 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. ---
[jira] [Commented] (HAWQ-891) Refine libyarn source codes
[ https://issues.apache.org/jira/browse/HAWQ-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363593#comment-15363593 ] ASF GitHub Bot commented on HAWQ-891: - GitHub user linwen opened a pull request: https://github.com/apache/incubator-hawq/pull/774 HAWQ-891. Refine libyarn codes Please review, thanks! You can merge this pull request into a Git repository by running: $ git pull https://github.com/linwen/incubator-hawq hawq-891 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/774.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #774 commit 383818c280f3b4787c726920105585c09bd7630f Author: Wen Lin Date: 2016-07-06T01:33:56Z HAWQ-891. Refine libyarn codes > Refine libyarn source codes > --- > > Key: HAWQ-891 > URL: https://issues.apache.org/jira/browse/HAWQ-891 > Project: Apache HAWQ > Issue Type: Bug > Components: libyarn >Reporter: Lin Wen >Assignee: Lin Wen > > Some parts of libyarn source codes need to be refined. > 1. some definition of exception in exception.h are useless; e.g. > FileAlreadyExistsException > 2. some interface need to be changed. e.g. constructor of class > LibYarnNodeInfo, use C++ string instead of char*; > 3. fix misspelling, e.g. "contaier" should be "container" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-891) Refine libyarn source codes
[ https://issues.apache.org/jira/browse/HAWQ-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363595#comment-15363595 ] ASF GitHub Bot commented on HAWQ-891: - Github user yaoj2 commented on the issue: https://github.com/apache/incubator-hawq/pull/774 LGTM > Refine libyarn source codes > --- > > Key: HAWQ-891 > URL: https://issues.apache.org/jira/browse/HAWQ-891 > Project: Apache HAWQ > Issue Type: Bug > Components: libyarn >Reporter: Lin Wen >Assignee: Lin Wen > > Some parts of libyarn source codes need to be refined. > 1. some definition of exception in exception.h are useless; e.g. > FileAlreadyExistsException > 2. some interface need to be changed. e.g. constructor of class > LibYarnNodeInfo, use C++ string instead of char*; > 3. fix misspelling, e.g. "contaier" should be "container" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #774: HAWQ-891. Refine libyarn codes
Github user liming01 commented on the issue: https://github.com/apache/incubator-hawq/pull/774 +1. --- 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 issue #774: HAWQ-891. Refine libyarn codes
Github user yaoj2 commented on the issue: https://github.com/apache/incubator-hawq/pull/774 LGTM --- 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. ---
[jira] [Commented] (HAWQ-891) Refine libyarn source codes
[ https://issues.apache.org/jira/browse/HAWQ-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363596#comment-15363596 ] ASF GitHub Bot commented on HAWQ-891: - Github user liming01 commented on the issue: https://github.com/apache/incubator-hawq/pull/774 +1. > Refine libyarn source codes > --- > > Key: HAWQ-891 > URL: https://issues.apache.org/jira/browse/HAWQ-891 > Project: Apache HAWQ > Issue Type: Bug > Components: libyarn >Reporter: Lin Wen >Assignee: Lin Wen > > Some parts of libyarn source codes need to be refined. > 1. some definition of exception in exception.h are useless; e.g. > FileAlreadyExistsException > 2. some interface need to be changed. e.g. constructor of class > LibYarnNodeInfo, use C++ string instead of char*; > 3. fix misspelling, e.g. "contaier" should be "container" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #774: HAWQ-891. Refine libyarn codes
Github user asfgit closed the pull request at: https://github.com/apache/incubator-hawq/pull/774 --- 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. ---
[jira] [Commented] (HAWQ-891) Refine libyarn source codes
[ https://issues.apache.org/jira/browse/HAWQ-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363597#comment-15363597 ] ASF GitHub Bot commented on HAWQ-891: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-hawq/pull/774 > Refine libyarn source codes > --- > > Key: HAWQ-891 > URL: https://issues.apache.org/jira/browse/HAWQ-891 > Project: Apache HAWQ > Issue Type: Bug > Components: libyarn >Reporter: Lin Wen >Assignee: Lin Wen > > Some parts of libyarn source codes need to be refined. > 1. some definition of exception in exception.h are useless; e.g. > FileAlreadyExistsException > 2. some interface need to be changed. e.g. constructor of class > LibYarnNodeInfo, use C++ string instead of char*; > 3. fix misspelling, e.g. "contaier" should be "container" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-893) Incorrect array indexing in load_expected_statuses() in pg_regress.c
Kavinder Dhaliwal created HAWQ-893: -- Summary: Incorrect array indexing in load_expected_statuses() in pg_regress.c Key: HAWQ-893 URL: https://issues.apache.org/jira/browse/HAWQ-893 Project: Apache HAWQ Issue Type: Bug Reporter: Kavinder Dhaliwal Assignee: Lei Chang Sometimes when running installcheck good there can be a case where when parsing a line from the src/test/regress/expected_statuses file the string that contains the name of the test will have its zero byte set to the null character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #773: HAWQ-888. Remove some dummy files which were used...
Github user xunzhang commented on the issue: https://github.com/apache/incubator-hawq/pull/773 LGMT --- 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. ---
[jira] [Commented] (HAWQ-888) Remove some dummy files which were used to keep related "empty" directories.
[ https://issues.apache.org/jira/browse/HAWQ-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363609#comment-15363609 ] ASF GitHub Bot commented on HAWQ-888: - Github user xunzhang commented on the issue: https://github.com/apache/incubator-hawq/pull/773 LGMT > Remove some dummy files which were used to keep related "empty" directories. > > > Key: HAWQ-888 > URL: https://issues.apache.org/jira/browse/HAWQ-888 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: Paul Guo >Assignee: Paul Guo > > After building with pgcrypto, plr, orca, the git repos will have the > following tracked files. > Changes not staged for commit: > (use "git add/rm ..." to update what will be committed) > (use "git checkout -- ..." to discard changes in working directory) > deleted:gp-xerces/git_keep_empty_directory.readme > deleted:gporca/git_keep_empty_directory.readme > deleted:gpos/git_keep_empty_directory.readme > deleted:postgres/git_keep_empty_directory.readme > deleted:../../src/pl/plr/git_keep_empty_directory.readme > Those files are just to remind developers to not write the directory (git > does not save empty directories). This is really annoying. .gitignore does > not resolve this issue. > A simple and elegant solution is: > git update-index --assume-unchanged > however followering error is seen after parallel building, > fatal: Unable to create '/data2/github/incubator-hawq/.git/index.lock': File > exists. > If no other git process is currently running, this probably means a > git process crashed in this repository earlier. Make sure no other git > process is running and remove the file manually to continue. > I do not want to waste too much time in digging into git internals, instead, > I'd try another simple solution: > - rm -f git_keep_empty_directory.readme; \ > + mv -f gporca.git_keep_empty_directory.readme ..; \ > [ ! -d .git ] && git clone $(gporca_git) . && git checkout > $(gporca_branch); \ > + mv -f ../gporca.git_keep_empty_directory.readme .; \ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HAWQ-891) Refine libyarn source codes
[ https://issues.apache.org/jira/browse/HAWQ-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Wen resolved HAWQ-891. -- Resolution: Fixed > Refine libyarn source codes > --- > > Key: HAWQ-891 > URL: https://issues.apache.org/jira/browse/HAWQ-891 > Project: Apache HAWQ > Issue Type: Bug > Components: libyarn >Reporter: Lin Wen >Assignee: Lin Wen > > Some parts of libyarn source codes need to be refined. > 1. some definition of exception in exception.h are useless; e.g. > FileAlreadyExistsException > 2. some interface need to be changed. e.g. constructor of class > LibYarnNodeInfo, use C++ string instead of char*; > 3. fix misspelling, e.g. "contaier" should be "container" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #775: HAWQ-893. Only copy and index status_str_l...
GitHub user kavinderd opened a pull request: https://github.com/apache/incubator-hawq/pull/775 HAWQ-893. Only copy and index status_str_length Previously status_str was being indexed with a value that overflowed its expected length and would zero-out the string 'test' You can merge this pull request into a Git repository by running: $ git pull https://github.com/kavinderd/incubator-hawq HAWQ-893 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/775.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #775 commit ad965c3cfe2a559340ad82675f289eebecb91a7a Author: Kavinder Dhaliwal Date: 2016-07-06T02:00:26Z HAWQ-893. Only copy and index status_str_length Previously status_str was being indexed with a value that overflowed its expected length and would zero-out the string 'test' --- 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. ---
[jira] [Commented] (HAWQ-893) Incorrect array indexing in load_expected_statuses() in pg_regress.c
[ https://issues.apache.org/jira/browse/HAWQ-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363623#comment-15363623 ] ASF GitHub Bot commented on HAWQ-893: - GitHub user kavinderd opened a pull request: https://github.com/apache/incubator-hawq/pull/775 HAWQ-893. Only copy and index status_str_length Previously status_str was being indexed with a value that overflowed its expected length and would zero-out the string 'test' You can merge this pull request into a Git repository by running: $ git pull https://github.com/kavinderd/incubator-hawq HAWQ-893 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/775.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #775 commit ad965c3cfe2a559340ad82675f289eebecb91a7a Author: Kavinder Dhaliwal Date: 2016-07-06T02:00:26Z HAWQ-893. Only copy and index status_str_length Previously status_str was being indexed with a value that overflowed its expected length and would zero-out the string 'test' > Incorrect array indexing in load_expected_statuses() in pg_regress.c > > > Key: HAWQ-893 > URL: https://issues.apache.org/jira/browse/HAWQ-893 > Project: Apache HAWQ > Issue Type: Bug >Reporter: Kavinder Dhaliwal >Assignee: Lei Chang > > Sometimes when running installcheck good there can be a case where when > parsing a line from the src/test/regress/expected_statuses file the string > that contains the name of the test will have its zero byte set to the null > character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-893) Incorrect array indexing in load_expected_statuses() in pg_regress.c
[ https://issues.apache.org/jira/browse/HAWQ-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kavinder Dhaliwal reassigned HAWQ-893: -- Assignee: Kavinder Dhaliwal (was: Lei Chang) > Incorrect array indexing in load_expected_statuses() in pg_regress.c > > > Key: HAWQ-893 > URL: https://issues.apache.org/jira/browse/HAWQ-893 > Project: Apache HAWQ > Issue Type: Bug >Reporter: Kavinder Dhaliwal >Assignee: Kavinder Dhaliwal > > Sometimes when running installcheck good there can be a case where when > parsing a line from the src/test/regress/expected_statuses file the string > that contains the name of the test will have its zero byte set to the null > character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #773: HAWQ-888. Remove some dummy files which we...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-hawq/pull/773 --- 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. ---
[jira] [Commented] (HAWQ-888) Remove some dummy files which were used to keep related "empty" directories.
[ https://issues.apache.org/jira/browse/HAWQ-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363635#comment-15363635 ] ASF GitHub Bot commented on HAWQ-888: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-hawq/pull/773 > Remove some dummy files which were used to keep related "empty" directories. > > > Key: HAWQ-888 > URL: https://issues.apache.org/jira/browse/HAWQ-888 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: Paul Guo >Assignee: Paul Guo > > After building with pgcrypto, plr, orca, the git repos will have the > following tracked files. > Changes not staged for commit: > (use "git add/rm ..." to update what will be committed) > (use "git checkout -- ..." to discard changes in working directory) > deleted:gp-xerces/git_keep_empty_directory.readme > deleted:gporca/git_keep_empty_directory.readme > deleted:gpos/git_keep_empty_directory.readme > deleted:postgres/git_keep_empty_directory.readme > deleted:../../src/pl/plr/git_keep_empty_directory.readme > Those files are just to remind developers to not write the directory (git > does not save empty directories). This is really annoying. .gitignore does > not resolve this issue. > A simple and elegant solution is: > git update-index --assume-unchanged > however followering error is seen after parallel building, > fatal: Unable to create '/data2/github/incubator-hawq/.git/index.lock': File > exists. > If no other git process is currently running, this probably means a > git process crashed in this repository earlier. Make sure no other git > process is running and remove the file manually to continue. > I do not want to waste too much time in digging into git internals, instead, > I'd try another simple solution: > - rm -f git_keep_empty_directory.readme; \ > + mv -f gporca.git_keep_empty_directory.readme ..; \ > [ ! -d .git ] && git clone $(gporca_git) . && git checkout > $(gporca_branch); \ > + mv -f ../gporca.git_keep_empty_directory.readme .; \ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #775: HAWQ-893. Only copy and index status_str_length
Github user yaoj2 commented on the issue: https://github.com/apache/incubator-hawq/pull/775 LGTM --- 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. ---
[jira] [Commented] (HAWQ-893) Incorrect array indexing in load_expected_statuses() in pg_regress.c
[ https://issues.apache.org/jira/browse/HAWQ-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363637#comment-15363637 ] ASF GitHub Bot commented on HAWQ-893: - Github user yaoj2 commented on the issue: https://github.com/apache/incubator-hawq/pull/775 LGTM > Incorrect array indexing in load_expected_statuses() in pg_regress.c > > > Key: HAWQ-893 > URL: https://issues.apache.org/jira/browse/HAWQ-893 > Project: Apache HAWQ > Issue Type: Bug >Reporter: Kavinder Dhaliwal >Assignee: Kavinder Dhaliwal > > Sometimes when running installcheck good there can be a case where when > parsing a line from the src/test/regress/expected_statuses file the string > that contains the name of the test will have its zero byte set to the null > character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-893) Incorrect array indexing in load_expected_statuses() in pg_regress.c
[ https://issues.apache.org/jira/browse/HAWQ-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363639#comment-15363639 ] ASF GitHub Bot commented on HAWQ-893: - Github user liming01 commented on the issue: https://github.com/apache/incubator-hawq/pull/775 +1. > Incorrect array indexing in load_expected_statuses() in pg_regress.c > > > Key: HAWQ-893 > URL: https://issues.apache.org/jira/browse/HAWQ-893 > Project: Apache HAWQ > Issue Type: Bug >Reporter: Kavinder Dhaliwal >Assignee: Kavinder Dhaliwal > > Sometimes when running installcheck good there can be a case where when > parsing a line from the src/test/regress/expected_statuses file the string > that contains the name of the test will have its zero byte set to the null > character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #775: HAWQ-893. Only copy and index status_str_length
Github user liming01 commented on the issue: https://github.com/apache/incubator-hawq/pull/775 +1. --- 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. ---
[jira] [Closed] (HAWQ-888) Remove some dummy files which were used to keep related "empty" directories.
[ https://issues.apache.org/jira/browse/HAWQ-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Guo closed HAWQ-888. - Resolution: Fixed > Remove some dummy files which were used to keep related "empty" directories. > > > Key: HAWQ-888 > URL: https://issues.apache.org/jira/browse/HAWQ-888 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: Paul Guo >Assignee: Paul Guo > > After building with pgcrypto, plr, orca, the git repos will have the > following tracked files. > Changes not staged for commit: > (use "git add/rm ..." to update what will be committed) > (use "git checkout -- ..." to discard changes in working directory) > deleted:gp-xerces/git_keep_empty_directory.readme > deleted:gporca/git_keep_empty_directory.readme > deleted:gpos/git_keep_empty_directory.readme > deleted:postgres/git_keep_empty_directory.readme > deleted:../../src/pl/plr/git_keep_empty_directory.readme > Those files are just to remind developers to not write the directory (git > does not save empty directories). This is really annoying. .gitignore does > not resolve this issue. > A simple and elegant solution is: > git update-index --assume-unchanged > however followering error is seen after parallel building, > fatal: Unable to create '/data2/github/incubator-hawq/.git/index.lock': File > exists. > If no other git process is currently running, this probably means a > git process crashed in this repository earlier. Make sure no other git > process is running and remove the file manually to continue. > I do not want to waste too much time in digging into git internals, instead, > I'd try another simple solution: > - rm -f git_keep_empty_directory.readme; \ > + mv -f gporca.git_keep_empty_directory.readme ..; \ > [ ! -d .git ] && git clone $(gporca_git) . && git checkout > $(gporca_branch); \ > + mv -f ../gporca.git_keep_empty_directory.readme .; \ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #775: HAWQ-893. Only copy and index status_str_l...
Github user kavinderd closed the pull request at: https://github.com/apache/incubator-hawq/pull/775 --- 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. ---
[jira] [Commented] (HAWQ-893) Incorrect array indexing in load_expected_statuses() in pg_regress.c
[ https://issues.apache.org/jira/browse/HAWQ-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363690#comment-15363690 ] ASF GitHub Bot commented on HAWQ-893: - Github user kavinderd commented on the issue: https://github.com/apache/incubator-hawq/pull/775 Merged > Incorrect array indexing in load_expected_statuses() in pg_regress.c > > > Key: HAWQ-893 > URL: https://issues.apache.org/jira/browse/HAWQ-893 > Project: Apache HAWQ > Issue Type: Bug >Reporter: Kavinder Dhaliwal >Assignee: Kavinder Dhaliwal > > Sometimes when running installcheck good there can be a case where when > parsing a line from the src/test/regress/expected_statuses file the string > that contains the name of the test will have its zero byte set to the null > character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #775: HAWQ-893. Only copy and index status_str_length
Github user kavinderd commented on the issue: https://github.com/apache/incubator-hawq/pull/775 Merged --- 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. ---
[jira] [Commented] (HAWQ-893) Incorrect array indexing in load_expected_statuses() in pg_regress.c
[ https://issues.apache.org/jira/browse/HAWQ-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363689#comment-15363689 ] ASF GitHub Bot commented on HAWQ-893: - Github user kavinderd closed the pull request at: https://github.com/apache/incubator-hawq/pull/775 > Incorrect array indexing in load_expected_statuses() in pg_regress.c > > > Key: HAWQ-893 > URL: https://issues.apache.org/jira/browse/HAWQ-893 > Project: Apache HAWQ > Issue Type: Bug >Reporter: Kavinder Dhaliwal >Assignee: Kavinder Dhaliwal > > Sometimes when running installcheck good there can be a case where when > parsing a line from the src/test/regress/expected_statuses file the string > that contains the name of the test will have its zero byte set to the null > character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #776: HAWQ-891. Fix functiontest build error
GitHub user linwen opened a pull request: https://github.com/apache/incubator-hawq/pull/776 HAWQ-891. Fix functiontest build error Please review, Thanks! You can merge this pull request into a Git repository by running: $ git pull https://github.com/linwen/incubator-hawq hawq-fix-891 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/776.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #776 commit 87d37f08e9278f9afd555fe501bd7f7ffafea8e9 Author: Wen Lin Date: 2016-07-06T03:42:49Z HAWQ-891. Fix functiontest build error --- 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. ---
[jira] [Commented] (HAWQ-891) Refine libyarn source codes
[ https://issues.apache.org/jira/browse/HAWQ-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363707#comment-15363707 ] ASF GitHub Bot commented on HAWQ-891: - GitHub user linwen opened a pull request: https://github.com/apache/incubator-hawq/pull/776 HAWQ-891. Fix functiontest build error Please review, Thanks! You can merge this pull request into a Git repository by running: $ git pull https://github.com/linwen/incubator-hawq hawq-fix-891 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/776.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #776 commit 87d37f08e9278f9afd555fe501bd7f7ffafea8e9 Author: Wen Lin Date: 2016-07-06T03:42:49Z HAWQ-891. Fix functiontest build error > Refine libyarn source codes > --- > > Key: HAWQ-891 > URL: https://issues.apache.org/jira/browse/HAWQ-891 > Project: Apache HAWQ > Issue Type: Bug > Components: libyarn >Reporter: Lin Wen >Assignee: Lin Wen > > Some parts of libyarn source codes need to be refined. > 1. some definition of exception in exception.h are useless; e.g. > FileAlreadyExistsException > 2. some interface need to be changed. e.g. constructor of class > LibYarnNodeInfo, use C++ string instead of char*; > 3. fix misspelling, e.g. "contaier" should be "container" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #776: HAWQ-891. Fix functiontest build error
Github user jinyismilodon commented on the issue: https://github.com/apache/incubator-hawq/pull/776 +1 LGTM --- 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. ---
[jira] [Commented] (HAWQ-891) Refine libyarn source codes
[ https://issues.apache.org/jira/browse/HAWQ-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363712#comment-15363712 ] ASF GitHub Bot commented on HAWQ-891: - Github user jinyismilodon commented on the issue: https://github.com/apache/incubator-hawq/pull/776 +1 LGTM > Refine libyarn source codes > --- > > Key: HAWQ-891 > URL: https://issues.apache.org/jira/browse/HAWQ-891 > Project: Apache HAWQ > Issue Type: Bug > Components: libyarn >Reporter: Lin Wen >Assignee: Lin Wen > > Some parts of libyarn source codes need to be refined. > 1. some definition of exception in exception.h are useless; e.g. > FileAlreadyExistsException > 2. some interface need to be changed. e.g. constructor of class > LibYarnNodeInfo, use C++ string instead of char*; > 3. fix misspelling, e.g. "contaier" should be "container" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #776: HAWQ-891. Fix functiontest build error
Github user liming01 commented on the issue: https://github.com/apache/incubator-hawq/pull/776 +1. --- 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 issue #776: HAWQ-891. Fix functiontest build error
Github user jiny2 commented on the issue: https://github.com/apache/incubator-hawq/pull/776 +1 LGTM --- 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. ---
[jira] [Commented] (HAWQ-891) Refine libyarn source codes
[ https://issues.apache.org/jira/browse/HAWQ-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363714#comment-15363714 ] ASF GitHub Bot commented on HAWQ-891: - Github user liming01 commented on the issue: https://github.com/apache/incubator-hawq/pull/776 +1. > Refine libyarn source codes > --- > > Key: HAWQ-891 > URL: https://issues.apache.org/jira/browse/HAWQ-891 > Project: Apache HAWQ > Issue Type: Bug > Components: libyarn >Reporter: Lin Wen >Assignee: Lin Wen > > Some parts of libyarn source codes need to be refined. > 1. some definition of exception in exception.h are useless; e.g. > FileAlreadyExistsException > 2. some interface need to be changed. e.g. constructor of class > LibYarnNodeInfo, use C++ string instead of char*; > 3. fix misspelling, e.g. "contaier" should be "container" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-891) Refine libyarn source codes
[ https://issues.apache.org/jira/browse/HAWQ-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363716#comment-15363716 ] ASF GitHub Bot commented on HAWQ-891: - Github user jiny2 commented on the issue: https://github.com/apache/incubator-hawq/pull/776 +1 LGTM > Refine libyarn source codes > --- > > Key: HAWQ-891 > URL: https://issues.apache.org/jira/browse/HAWQ-891 > Project: Apache HAWQ > Issue Type: Bug > Components: libyarn >Reporter: Lin Wen >Assignee: Lin Wen > > Some parts of libyarn source codes need to be refined. > 1. some definition of exception in exception.h are useless; e.g. > FileAlreadyExistsException > 2. some interface need to be changed. e.g. constructor of class > LibYarnNodeInfo, use C++ string instead of char*; > 3. fix misspelling, e.g. "contaier" should be "container" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #776: HAWQ-891. Fix functiontest build error
Github user asfgit closed the pull request at: https://github.com/apache/incubator-hawq/pull/776 --- 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. ---
[jira] [Commented] (HAWQ-891) Refine libyarn source codes
[ https://issues.apache.org/jira/browse/HAWQ-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363721#comment-15363721 ] ASF GitHub Bot commented on HAWQ-891: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-hawq/pull/776 > Refine libyarn source codes > --- > > Key: HAWQ-891 > URL: https://issues.apache.org/jira/browse/HAWQ-891 > Project: Apache HAWQ > Issue Type: Bug > Components: libyarn >Reporter: Lin Wen >Assignee: Lin Wen > > Some parts of libyarn source codes need to be refined. > 1. some definition of exception in exception.h are useless; e.g. > FileAlreadyExistsException > 2. some interface need to be changed. e.g. constructor of class > LibYarnNodeInfo, use C++ string instead of char*; > 3. fix misspelling, e.g. "contaier" should be "container" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-894) Add feature test for polymorphism with new test framework
Lin Wen created HAWQ-894: Summary: Add feature test for polymorphism with new test framework Key: HAWQ-894 URL: https://issues.apache.org/jira/browse/HAWQ-894 Project: Apache HAWQ Issue Type: Sub-task Components: Tests Reporter: Lin Wen Assignee: Jiali Yao -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-894) Add feature test for polymorphism with new test framework
[ https://issues.apache.org/jira/browse/HAWQ-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Wen reassigned HAWQ-894: Assignee: Lin Wen (was: Jiali Yao) > Add feature test for polymorphism with new test framework > - > > Key: HAWQ-894 > URL: https://issues.apache.org/jira/browse/HAWQ-894 > Project: Apache HAWQ > Issue Type: Sub-task > Components: Tests >Reporter: Lin Wen >Assignee: Lin Wen > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-895) Investigate migration to 3-digit Semantic versioning
Vineet Goel created HAWQ-895: Summary: Investigate migration to 3-digit Semantic versioning Key: HAWQ-895 URL: https://issues.apache.org/jira/browse/HAWQ-895 Project: Apache HAWQ Issue Type: Task Components: Core Reporter: Vineet Goel Assignee: Lei Chang Current HAWQ code is tied to 4-digit versioning which is related to the library compatibility and inherited from old Postgres. We should investigate the impact of switching to 3-digit Semantic versioning (http://semver.org) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #777: HAWQ-825. Add log to hawq reload cluster
GitHub user radarwave opened a pull request: https://github.com/apache/incubator-hawq/pull/777 HAWQ-825. Add log to hawq reload cluster Add log: Reloading configuration without restarting hawq cluster You can merge this pull request into a Git repository by running: $ git pull https://github.com/radarwave/incubator-hawq stopu Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/777.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #777 commit f81a35756898b09524264bcea9f8721c571b0f4c Author: rlei Date: 2016-07-06T05:20:41Z HAWQ-825. Add log to hawq reload cluster --- 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. ---
[jira] [Commented] (HAWQ-825) HAWQ component reload shows misleading message on stdout
[
https://issues.apache.org/jira/browse/HAWQ-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363792#comment-15363792
]
ASF GitHub Bot commented on HAWQ-825:
-
GitHub user radarwave opened a pull request:
https://github.com/apache/incubator-hawq/pull/777
HAWQ-825. Add log to hawq reload cluster
Add log:
Reloading configuration without restarting hawq cluster
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/radarwave/incubator-hawq stopu
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq/pull/777.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #777
commit f81a35756898b09524264bcea9f8721c571b0f4c
Author: rlei
Date: 2016-07-06T05:20:41Z
HAWQ-825. Add log to hawq reload cluster
> HAWQ component reload shows misleading message on stdout
>
>
> Key: HAWQ-825
> URL: https://issues.apache.org/jira/browse/HAWQ-825
> Project: Apache HAWQ
> Issue Type: Bug
>Reporter: Matt
>Assignee: Radar Lei
> Attachments: stdout.png
>
>
> After running {code}hawq stop master -u{code}, the message on the stdout says
> the master was successfully stopped.
> The -u option does not stop the master, it only reloads the configurations.
> The stdout message should be changed for this operation, so that it does not
> mislead the user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HAWQ-896) Add feature test for create table with new test framework
Lin Wen created HAWQ-896: Summary: Add feature test for create table with new test framework Key: HAWQ-896 URL: https://issues.apache.org/jira/browse/HAWQ-896 Project: Apache HAWQ Issue Type: Sub-task Components: Tests Reporter: Lin Wen Assignee: Jiali Yao -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (HAWQ-882) insert failed when compresstype=gzip
[ https://issues.apache.org/jira/browse/HAWQ-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liuguo closed HAWQ-882. --- Resolution: Fixed > insert failed when compresstype=gzip > > > Key: HAWQ-882 > URL: https://issues.apache.org/jira/browse/HAWQ-882 > Project: Apache HAWQ > Issue Type: Bug >Reporter: liuguo >Assignee: Lei Chang > > create sql is : > create table testzip(a int, b varchar(20))with(appendonly=true, > orientation=parquet, compresstype=gzip, compresslevel=8); > Inserting a record at a time is no problem. > But error inserting 1 records at one time > the error is: > psycopg2.OperationalError: Parquet Storage Write error on segment file > 'hdfs://kmaster:8020/hawq_default/16385/16535/16569/1': writing footer file > failure (seg0 kslave1:4 pid=790454) > > create sql is:create table testzip1(a int, b > varchar(20))with(appendonly=true, orientation=parquet, compresstype=snappy); > when the table's compresstype=snappy , get an error: > ERROR: Parquet Storage Write error on segment file > 'hdfs://kmaster:8020/hawq_default/16385/16535/16564/1': writing footer file > failure (seg0 kslave2:4 pid=441973) > > create sql is:create table testzip2(a int, b > varchar(20))with(appendonly=true, compresstype=quicklz, compresslevel=1); > when the table's compesstype=quicklz, get an error: > ERROR: Could not flush (fsync) Append-Only segment file > 'hdfs://kmaster:8020/hawq_default/16385/16535/16556/1' to disk for relation > 'testquicklz': Input/output error (seg0 kslave1:4 pid=4112) > DETAIL: > File /hawq_default/16385/16535/16556/1 could only be replicated to 0 nodes > instead of minReplication (=1). There are 2 datanode(s) running and no > node(s) are excluded in this operation. > at > org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget4NewBlock(BlockManager.java:1559) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:3245) > at > org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:663) > at > org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:482) > at > org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java) > at > org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:619) > at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:975) > at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2040) > at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2036) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1656) > my hadoop have 2 nodes, version is 2.7.1.2.4 > my hawq have 2 nodes , version is 2.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-897) Add feature test for create table distribution with new test framework
Lin Wen created HAWQ-897: Summary: Add feature test for create table distribution with new test framework Key: HAWQ-897 URL: https://issues.apache.org/jira/browse/HAWQ-897 Project: Apache HAWQ Issue Type: Sub-task Components: Tests Reporter: Lin Wen Assignee: Jiali Yao -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-898) Add feature test for COPY with new test framework
Lin Wen created HAWQ-898: Summary: Add feature test for COPY with new test framework Key: HAWQ-898 URL: https://issues.apache.org/jira/browse/HAWQ-898 Project: Apache HAWQ Issue Type: Sub-task Components: Tests Reporter: Lin Wen Assignee: Jiali Yao -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HAWQ-899) Add feature test for nested null case with new test framework
Lin Wen created HAWQ-899: Summary: Add feature test for nested null case with new test framework Key: HAWQ-899 URL: https://issues.apache.org/jira/browse/HAWQ-899 Project: Apache HAWQ Issue Type: Sub-task Components: Tests Reporter: Lin Wen Assignee: Jiali Yao -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-899) Add feature test for nested null case with new test framework
[ https://issues.apache.org/jira/browse/HAWQ-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Wen reassigned HAWQ-899: Assignee: Lin Wen (was: Jiali Yao) > Add feature test for nested null case with new test framework > - > > Key: HAWQ-899 > URL: https://issues.apache.org/jira/browse/HAWQ-899 > Project: Apache HAWQ > Issue Type: Sub-task > Components: Tests >Reporter: Lin Wen >Assignee: Lin Wen > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-896) Add feature test for create table with new test framework
[ https://issues.apache.org/jira/browse/HAWQ-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Wen reassigned HAWQ-896: Assignee: Lin Wen (was: Jiali Yao) > Add feature test for create table with new test framework > - > > Key: HAWQ-896 > URL: https://issues.apache.org/jira/browse/HAWQ-896 > Project: Apache HAWQ > Issue Type: Sub-task > Components: Tests >Reporter: Lin Wen >Assignee: Lin Wen > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-898) Add feature test for COPY with new test framework
[ https://issues.apache.org/jira/browse/HAWQ-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Wen reassigned HAWQ-898: Assignee: Lin Wen (was: Jiali Yao) > Add feature test for COPY with new test framework > -- > > Key: HAWQ-898 > URL: https://issues.apache.org/jira/browse/HAWQ-898 > Project: Apache HAWQ > Issue Type: Sub-task > Components: Tests >Reporter: Lin Wen >Assignee: Lin Wen > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HAWQ-897) Add feature test for create table distribution with new test framework
[ https://issues.apache.org/jira/browse/HAWQ-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Wen reassigned HAWQ-897: Assignee: Lin Wen (was: Jiali Yao) > Add feature test for create table distribution with new test framework > -- > > Key: HAWQ-897 > URL: https://issues.apache.org/jira/browse/HAWQ-897 > Project: Apache HAWQ > Issue Type: Sub-task > Components: Tests >Reporter: Lin Wen >Assignee: Lin Wen > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
