[
https://issues.apache.org/jira/browse/MADLIB-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883680#comment-15883680
]
ASF GitHub Bot commented on MADLIB-1024:
----------------------------------------
GitHub user iyerr3 opened a pull request:
https://github.com/apache/incubator-madlib/pull/106
Build: Fix module sort order for PGXN installation
JIRA: MADLIB-1024
PGXN installation involves creating a single extension sql file that
contains all the SQL commands run during MADlib deployment. The modules
added into this extension file are to be placed in the right order,
taking dependencies into account.
MADlib has a function that compares a given file path with topologically
sorted modules to decide the order of concatenation to extension file.
This comparison is faulty since the module name was searched for in the
whole path, leading to false positive with modules that have another
module name as substring. The specific bug was related to 'svec_util'
being flagged in same order as 'svec'.
This commit fixes this issue taking advantage of the file path names being
of the form '.../modules/<module_name>/...', hence comparing the
complete module name.
Closes #106
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/iyerr3/incubator-madlib
bugfix/module_sort_order
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-madlib/pull/106.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 #106
----
commit b106e064edf5d3d03631d222a51953d0d21015d4
Author: Rahul Iyer <[email protected]>
Date: 2017-02-24T22:32:32Z
Build: Fix module sort order for PGXN installation
JIRA: MADLIB-1024
PGXN installation involves creating a single extension sql file that
contains all the SQL commands run during MADlib deployment. The modules
added into this extension file are to be placed in the right order,
taking dependencies into account.
MADlib has a function that compares a given file path with topologically
sorted modules to decide the order of concatenation to extension file.
This comparison is faulty since the module name was searched for in the
whole path, leading to false positive with modules that have another
module name as substring. The specific bug was related to 'svec_util'
being flagged in same order as 'svec'.
This commit fixes this issue taking advantage of the file path names being
of the form '.../modules/<module_name>/...', hence comparing the
complete module name.
Closes #106
----
> CREATE EXTENSION madlib fails
> -----------------------------
>
> Key: MADLIB-1024
> URL: https://issues.apache.org/jira/browse/MADLIB-1024
> Project: Apache MADlib
> Issue Type: Bug
> Reporter: Martin Jensen
> Assignee: Orhan Kislal
> Fix For: v1.11
>
> Attachments: Dockerfile
>
>
> When installing madlib with PGXN on PG 9.5.4, Ubuntu 16.04 I get the
> following error when trying to create the extension:
> ERROR: aggregate cannot accept shell type public.svec
> ********** Error **********
> ERROR: aggregate cannot accept shell type public.svec
> SQL state: 42P13
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
