[jira] [Resolved] (MADLIB-1065) CMake: Give informative error message when no files found in serverdir

[Frank McQuillan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Frank McQuillan resolved MADLIB-1065.
-
Resolution: Fixed

> CMake: Give informative error message when no files found in serverdir 
> ---
>
> Key: MADLIB-1065
> URL: https://issues.apache.org/jira/browse/MADLIB-1065
> Project: Apache MADlib
>  Issue Type: Bug
>  Components: Build System
>Reporter: Rahul Iyer
>Priority: Minor
> Fix For: v1.11
>
>
> Error reported by user trying to compile MADlib on Ubuntu against Postgresql 
> 9.6. The postgres installation was missing server headers, which led to an 
> error during {{cmake}}. 
> The only error shown was: 
> {{-- Could NOT find PostgreSQL (missing:  POSTGRESQL_EXECUTABLE) }}. 
> This can be improved to give the actual source of error, with instructions on 
> how to fix. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (MADLIB-920) Build process on Apache infrastructure

[Frank McQuillan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Frank McQuillan resolved MADLIB-920.

Resolution: Fixed

> Build process on Apache infrastructure
> --
>
> Key: MADLIB-920
> URL: https://issues.apache.org/jira/browse/MADLIB-920
> Project: Apache MADlib
>  Issue Type: Test
>  Components: Build System
>Reporter: Frank McQuillan
>Assignee: Rahul Iyer
> Fix For: v1.11
>
>
> As a MADlib developer, I would like to build a complete docker file + image 
> with instructions on how to start/build/test MADlib, so that community 
> developers can use this to test.  Please put the file in src code, put 
> instructions on wiki.
> We are doing this in part because access to Apache Build system for MADlib 
> gives access to all incubating projects, and we don't want to facilitate that.
> Needed for graduation to TLP.
> The target platforms are:
> 1) PostgreSQL 9.6
> 2) gpdb 4.3.x (later 5.x)
> Please indicate of gpdb part is taking a ton of time and if so, maybe we live 
> with PG for now.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MADLIB-920) Build process on Apache infrastructure

[Nandish Jayaram (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868716#comment-15868716
 ] 

Nandish Jayaram commented on MADLIB-920:


Changes made to provide docker images with Postgres-9.6 and MADlib dependencies 
installed.
Another docker file that uses this image can be used to build, install and test 
MADlib. This is not
done for Greenplum yet, might be picked up as part of another JIRA.

> Build process on Apache infrastructure
> --
>
> Key: MADLIB-920
> URL: https://issues.apache.org/jira/browse/MADLIB-920
> Project: Apache MADlib
>  Issue Type: Test
>  Components: Build System
>Reporter: Frank McQuillan
>Assignee: Rahul Iyer
> Fix For: v1.11
>
>
> As a MADlib developer, I would like to build a complete docker file + image 
> with instructions on how to start/build/test MADlib, so that community 
> developers can use this to test.  Please put the file in src code, put 
> instructions on wiki.
> We are doing this in part because access to Apache Build system for MADlib 
> gives access to all incubating projects, and we don't want to facilitate that.
> Needed for graduation to TLP.
> The target platforms are:
> 1) PostgreSQL 9.6
> 2) gpdb 4.3.x (later 5.x)
> Please indicate of gpdb part is taking a ton of time and if so, maybe we live 
> with PG for now.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MADLIB-920) Build process on Apache infrastructure

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868708#comment-15868708
 ] 

ASF GitHub Bot commented on MADLIB-920:
---

GitHub user njayaram2 opened a pull request:

https://github.com/apache/incubator-madlib/pull/103

Docker Build for MADlib

JIRA: MADLIB-920

- Add docker files that would help developers download a docker image
with Postgres-9.6 and MADlib depedencies installed. A developer's
local source code changes can be built on this image's container
to quickly build and run install-checks. Requires docker installed
on the developer's environment.
- Add a bash script (jenkins_build.sh) that would be a starting
point towards getting a Jenkins build for MADlib master branch.
- This is work under heavy development and we would want to add in
similar support for Greenplum as well in the future. There is a
placeholder Dockerfile for GPDB in this commit, must be modified
to get it working.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/njayaram2/incubator-madlib docker-build

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-madlib/pull/103.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 #103


commit d9d9d296ec50272b2ce50ad1e975c78574ceaed2
Author: Nandish Jayaram 
Date:   2017-02-15T22:21:17Z

Docker Build for MADlib

JIRA: MADLIB-920

- Add docker files that would help developers download a docker image
with Postgres-9.6 and MADlib depedencies installed. A developer's
local source code changes can be built on this image's container
to quickly build and run install-checks. Requires docker installed
on the developer's environment.
- Add a bash script (jenkins_build.sh) that would be a starting
point towards getting a Jenkins build for MADlib master branch.
- This is work under heavy development and we would want to add in
similar support for Greenplum as well in the future. There is a
placeholder Dockerfile for GPDB in this commit, must be modified
to get it working.




> Build process on Apache infrastructure
> --
>
> Key: MADLIB-920
> URL: https://issues.apache.org/jira/browse/MADLIB-920
> Project: Apache MADlib
>  Issue Type: Test
>  Components: Build System
>Reporter: Frank McQuillan
>Assignee: Rahul Iyer
> Fix For: v1.11
>
>
> As a MADlib developer, I would like to build a complete docker file + image 
> with instructions on how to start/build/test MADlib, so that community 
> developers can use this to test.  Please put the file in src code, put 
> instructions on wiki.
> We are doing this in part because access to Apache Build system for MADlib 
> gives access to all incubating projects, and we don't want to facilitate that.
> Needed for graduation to TLP.
> The target platforms are:
> 1) PostgreSQL 9.6
> 2) gpdb 4.3.x (later 5.x)
> Please indicate of gpdb part is taking a ton of time and if so, maybe we live 
> with PG for now.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MADLIB-1024) CREATE EXTENSION madlib fails

[Frank McQuillan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Frank McQuillan updated MADLIB-1024:

Fix Version/s: (was: v1.10)
   v1.11

> 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)

[jira] [Comment Edited] (MADLIB-905) Automation for publishing module documentation on ASF infra

[Frank McQuillan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15240218#comment-15240218
 ] 

Frank McQuillan edited comment on MADLIB-905 at 2/15/17 6:33 PM:
-

Module docs have been moved to ASF infra as part of 1.9

Rest of this story for later to add more automation.


was (Author: fmcquillan):
Module docs have been moved to ASF infra as part of 1.9

Rest of this story for 1.9.1 is to add more automation.

> Automation for publishing module documentation on ASF infra
> ---
>
> Key: MADLIB-905
> URL: https://issues.apache.org/jira/browse/MADLIB-905
> Project: Apache MADlib
>  Issue Type: Documentation
>  Components: Documentation
>Reporter: Frank McQuillan
>Assignee: Rahul Iyer
> Fix For: v2.0
>
>
> Currently MADlib docs are generated using Doxygen and published to
> http://doc.madlib.net/latest/
> Need to move to Apache infra.
> Also please review and update links and instructions as required in this wiki:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61328921



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MADLIB-1021) Required tasks for graduation to ASF top-level project

[Frank McQuillan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Frank McQuillan updated MADLIB-1021:

Fix Version/s: (was: v2.0)
   v1.11

> Required tasks for graduation to ASF top-level project
> --
>
> Key: MADLIB-1021
> URL: https://issues.apache.org/jira/browse/MADLIB-1021
> Project: Apache MADlib
>  Issue Type: Epic
>  Components: All Modules
>Reporter: Frank McQuillan
>Assignee: Frank McQuillan
> Fix For: v1.11
>
>
> This epic describes the required tasks for graduation to ASF top-level 
> project.  This may include software, administrative and other items.
> Guidelines:
> http://incubator.apache.org/guides/graduation.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MADLIB-1074) Graph cut

[Frank McQuillan (JIRA)]

Frank McQuillan created MADLIB-1074:
---

 Summary: Graph cut
 Key: MADLIB-1074
 URL: https://issues.apache.org/jira/browse/MADLIB-1074
 Project: Apache MADlib
  Issue Type: New Feature
  Components: Module: Graph
Reporter: Frank McQuillan
 Fix For: v1.11


Story

As a data scientist, I want to partition a graph into k-partitions, so that I 
can work on the partitions separately, in part for performance reasons.

References

[1] "Multilevel k-way Partitioning Scheme for Irregular Graphs"​ , which talks 
about a scalable approach to partition a graph into k-partitions by first 
coarsening the graph, partitioning the coarsened graph into k parts and than 
un-coarsening later.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MADLIB-1073) Graph - measures

[Frank McQuillan (JIRA)]

Frank McQuillan created MADLIB-1073:
---

 Summary: Graph - measures
 Key: MADLIB-1073
 URL: https://issues.apache.org/jira/browse/MADLIB-1073
 Project: Apache MADlib
  Issue Type: New Feature
  Components: Module: Graph
Reporter: Frank McQuillan
 Fix For: v1.11


Story

As a MADlib developer, I want to implement the following measures primarily 
based on APSP:
* betweenness centrality
* closeness centrality
* graph diameter
* others?

Acceptance

1) Interface defined
2) Design document updated
3) Documentation and on-line help
4) IC and functional tests
5) Scale tests
6) Are there any other measures that can be easily calculated given that we 
have the following algos avail: SSSP, APSP, page rank,  weakly connected 
components?




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MADLIB-1072) Graph - all pairs shortest path

[Frank McQuillan (JIRA)]

Frank McQuillan created MADLIB-1072:
---

 Summary: Graph - all pairs shortest path
 Key: MADLIB-1072
 URL: https://issues.apache.org/jira/browse/MADLIB-1072
 Project: Apache MADlib
  Issue Type: New Feature
  Components: Module: Graph
Reporter: Frank McQuillan
 Fix For: v1.11


Story

As a MADlib developer, I want to implement all pairs shortest path in an 
efficient and scaleable manner.

Acceptance

1) Interface defined
2) Design document updated
3) Documentation and on-line help
4) IC and functional tests
5) Scale tests

Refs

[1] Floyd-Warshall is one possible implemention
https://en.wikipedia.org/wiki/Floyd%E2%80%93Warshall_algorithm




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MADLIB-1071) Graph - weakly connect components

[Frank McQuillan (JIRA)]

Frank McQuillan created MADLIB-1071:
---

 Summary: Graph - weakly connect components
 Key: MADLIB-1071
 URL: https://issues.apache.org/jira/browse/MADLIB-1071
 Project: Apache MADlib
  Issue Type: New Feature
  Components: Module: Graph
Reporter: Frank McQuillan
 Fix For: v1.11


Story

As a MADlib developer, I want to implement  weakly connected components (ref 
[0]) in an efficient and scaleable way.

Acceptance

1) Interface defined
2) Design document updated
3) Documentation and on-line help
4) IC and functional tests
5) Scale tests

References

[0] https://en.wikipedia.org/wiki/Connectivity_(graph_theory)
"A directed graph is called weakly connected if replacing all of its directed 
edges with undirected edges produces a connected (undirected) graph."

[1] Grails paper
http://pages.cs.wisc.edu/~jignesh/publ/Grail.pdf

[2] Grails deck
http://pages.cs.wisc.edu/~jignesh/publ/Grail-slides.pdf

[3] Grails repo with page rank example
https://github.com/UWQuickstep/Grail
https://github.com/UWQuickstep/Grail/blob/master/analytics/wcc.sql
(weakly connected components implementation)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MADLIB-1070) Graph - visualization

[Frank McQuillan (JIRA)]

Frank McQuillan created MADLIB-1070:
---

 Summary: Graph - visualization
 Key: MADLIB-1070
 URL: https://issues.apache.org/jira/browse/MADLIB-1070
 Project: Apache MADlib
  Issue Type: New Feature
  Components: Module: Graph
Reporter: Frank McQuillan
 Fix For: v1.11


Story 

As a data scientist, I want to export a graph in a form suitable for 
visualization, so that it makes my analysis easier and I can communicate 
findings more easily to others.

This is also useful for MADlib demos.

Export format TBD. Pivotal data science team likes Gephi [1].  Another option 
is GraphViz [2] which we support for decision trees.

References

[1] Gephi
https://gephi.org/

[2] GraphViz
http://www.graphviz.org/



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MADLIB-1069) Graph - page rank

[Frank McQuillan (JIRA)]

Frank McQuillan created MADLIB-1069:
---

 Summary: Graph - page rank
 Key: MADLIB-1069
 URL: https://issues.apache.org/jira/browse/MADLIB-1069
 Project: Apache MADlib
  Issue Type: New Feature
  Components: Module: Graph
Reporter: Frank McQuillan
 Fix For: v1.11


Story

As a MADlib developer, I want to implement page rank in an efficient and 
scaleable way.

Acceptance

1) Interface defined
2) Design document updated
3) Documentation and on-line help
4) IC and functional tests
5) Scale tests

References

[1] Grails paper
http://pages.cs.wisc.edu/~jignesh/publ/Grail.pdf

[2] Grails deck
http://pages.cs.wisc.edu/~jignesh/publ/Grail-slides.pdf

[3] Grails repo with page rank example
https://github.com/UWQuickstep/Grail
https://github.com/UWQuickstep/Grail/blob/master/analytics/pagerank.sql

[4] PDL tools implementation
http://pivotalsoftware.github.io/PDLTools/group__grp__pagerank__alg.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MADLIB-1066) Pivoting - support array and svec output

[Frank McQuillan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Frank McQuillan updated MADLIB-1066:

Fix Version/s: (was: v2.0)
   v1.11

> Pivoting - support array and svec output
> 
>
> Key: MADLIB-1066
> URL: https://issues.apache.org/jira/browse/MADLIB-1066
> Project: Apache MADlib
>  Issue Type: Improvement
>  Components: Module: Utilities
>Reporter: Frank McQuillan
>Priority: Minor
> Fix For: v1.11
>
>
> Background
> Follow on to these JIRAs
> https://issues.apache.org/jira/browse/MADLIB-908
> https://issues.apache.org/jira/browse/MADLIB-1004
> this capability is to carry over some good ideas from
> https://issues.apache.org/jira/browse/MADLIB-1038
> Story
> Support array output format to allow > 1600 output columns (or PostgreSQL 
> limit).  i.e., many MADlib algos take array input so pivot should support 
> array output.  Base this on how it is done in encoding categorical variables 
> http://madlib.incubator.apache.org/docs/latest/group__grp__encode__categorical.html
> Add 'output_type' to interface:
> {code}
> pivot(
> source_table,
> output_table,
> index,
> pivot_cols,
> pivot_values,
> aggregate_func,
> fill_value,
> keep_null,
> output_col_dictionary,
> output_type  -- New
> )
> {code}
> where
> {code}
> output_type (optional)
> VARCHAR. default: 'column'. This parameter controls the output format.  If 
> 'column', a column is created for each output variable. PostgreSQL limits the 
> number of columns in a table. If the total number of columns exceeds the 
> limit, then make this parameter either 'array' to combine the indicator 
> columns into an array or 'svec' to cast the array output to 'madlib.svec' 
> type.
> Since the array output for any single tuple would be sparse, the 'svec' 
> output would be most efficient for storage. The 'array' output is useful if 
> the array is used for post-processing, including concatenating with other 
> non-categorical features.
> A dictionary will be created when 'output_type' is 'array' or 'svec' to 
> define an index into the array. The dictionary table will be given the name 
> of the 'output_table' appended by '_dictionary'.
> {code}
> See code in
> http://madlib.incubator.apache.org/docs/latest/group__grp__encode__categorical.html
> need to support NULL (=default 'column').  Also 'a' and 'Array' and 'arr' 
> should be interpreted as 'array.  Same idea with 'column' and 'svec'



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MADLIB-1025) MADlib does not compile with gcc 6.2

[Frank McQuillan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Frank McQuillan updated MADLIB-1025:

Fix Version/s: (was: v2.0)
   v1.11

> MADlib does not compile with gcc 6.2
> 
>
> Key: MADLIB-1025
> URL: https://issues.apache.org/jira/browse/MADLIB-1025
> Project: Apache MADlib
>  Issue Type: Bug
>  Components: Build System
>Reporter: Rahul Iyer
>Assignee: Nandish Jayaram
>Priority: Minor
> Fix For: v1.11
>
>
> Compiling with gcc 6.2.0 gives the below error.
> {code}
> [ 84%] Building CXX object 
> src/ports/postgres/9.5/CMakeFiles/madlib_postgresql_9_5.dir/__/__/__/modules/elastic_net/elastic_net_gaussian_fista.cpp.o
> In file included from 
> /var/folders/rm/g9tb1s_53wb86s5_nrsdbxphgn/T/tmp8WXq3S/madlib-1.9.1/src/modules/elastic_net/elastic_net_binomial_igd.cpp:5:0:
> /var/folders/rm/g9tb1s_53wb86s5_nrsdbxphgn/T/tmp8WXq3S/madlib-1.9.1/src/modules/elastic_net/elastic_net_optimizer_igd.hpp:
>  In static member function 'static madlib::dbconnector::postgres::AnyType 
> madlib::modules::elastic_net::Igd<
> Model>::igd_transition(madlib::dbconnector::postgres::AnyType&, const 
> madlib::dbconnector::postgres::Allocator&)':
> /var/folders/rm/g9tb1s_53wb86s5_nrsdbxphgn/T/tmp8WXq3S/madlib-1.9.1/src/modules/elastic_net/elastic_net_optimizer_igd.hpp:69:46:
>  error: call of overloaded 
> 'log(madlib::modules::HandleTraits rayHandle >::ReferenceToUInt32&)' is ambiguous
>  state.p = 2 * log(state.dimension);
>   ^
> In file included from 
> /usr/local/Cellar/gcc/6.2.0/include/c++/6.2.0/cmath:45:0,
>  from /usr/local/Cellar/gcc/6.2.0/include/c++/6.2.0/math.h:36,
>  from 
> /var/folders/rm/g9tb1s_53wb86s5_nrsdbxphgn/T/tmp8WXq3S/madlib-1.9.1/src/ports/postgres/dbconnector/../../../../methods/svec/src/pg_gp/SparseData.h:24,
>  from 
> /var/folders/rm/g9tb1s_53wb86s5_nrsdbxphgn/T/tmp8WXq3S/madlib-1.9.1/src/ports/postgres/dbconnector/../../../../methods/svec/src/pg_gp/sparse_vector.h:10,
>  from 
> /var/folders/rm/g9tb1s_53wb86s5_nrsdbxphgn/T/tmp8WXq3S/madlib-1.9.1/src/ports/postgres/dbconnector/dbconnector.hpp:39,
>  from 
> /var/folders/rm/g9tb1s_53wb86s5_nrsdbxphgn/T/tmp8WXq3S/madlib-1.9.1/src/modules/elastic_net/elastic_net_binomial_igd.cpp:2:
> /usr/local/Cellar/gcc/6.2.0/lib/gcc/6/gcc/x86_64-apple-darwin15.6.0/6.2.0/include-fixed/math.h:402:15:
>  note: candidate: double log(double)
>  extern double log(double);
>^~~
> In file included from 
> /usr/local/Cellar/gcc/6.2.0/include/c++/6.2.0/math.h:36:0,
>  from 
> /var/folders/rm/g9tb1s_53wb86s5_nrsdbxphgn/T/tmp8WXq3S/madlib-1.9.1/src/ports/postgres/dbconnector/../../../../methods/svec/src/pg_gp/SparseData.h:24,
>  from 
> /var/folders/rm/g9tb1s_53wb86s5_nrsdbxphgn/T/tmp8WXq3S/madlib-1.9.1/src/ports/postgres/dbconnector/../../../../methods/svec/src/pg_gp/sparse_vector.h:10,
>  from 
> /var/folders/rm/g9tb1s_53wb86s5_nrsdbxphgn/T/tmp8WXq3S/madlib-1.9.1/src/ports/postgres/dbconnector/dbconnector.hpp:39,
>  from 
> /var/folders/rm/g9tb1s_53wb86s5_nrsdbxphgn/T/tmp8WXq3S/madlib-1.9.1/src/modules/elastic_net/elastic_net_binomial_igd.cpp:2:
> /usr/local/Cellar/gcc/6.2.0/include/c++/6.2.0/cmath:365:3: note: candidate: 
> long double std::log(long double)
>log(long double __x)
>^~~
> /usr/local/Cellar/gcc/6.2.0/include/c++/6.2.0/cmath:361:3: note: candidate: 
> float std::log(float)
>log(float __x)
>^~~
> make[3]: *** 
> [src/ports/postgres/9.5/CMakeFiles/madlib_postgresql_9_5.dir/__/__/__/modules/elastic_net/elastic_net_binomial_igd.cpp.o]
>  Error 1
> make[3]: *** Waiting for unfinished jobs
> make[2]: *** 
> [src/ports/postgres/9.5/CMakeFiles/madlib_postgresql_9_5.dir/all] Error 2
> make[1]: *** [all] Error 2
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MADLIB-920) Build process on Apache infrastructure

[Frank McQuillan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Frank McQuillan updated MADLIB-920:
---
Description: 
As a MADlib developer, I would like to build a complete docker file + image 
with instructions on how to start/build/test MADlib, so that community 
developers can use this to test.  Please put the file in src code, put 
instructions on wiki.

We are doing this in part because access to Apache Build system for MADlib 
gives access to all incubating projects, and we don't want to facilitate that.

Needed for graduation to TLP.

The target platforms are:
1) PostgreSQL 9.6
2) gpdb 4.3.x (later 5.x)

Please indicate of gpdb part is taking a ton of time and if so, maybe we live 
with PG for now.



  was:
As a MADlib developer, I would like to implement a build process on Apache 
infrastructure https://builds.apache.org/, so that I can ensure that 
contributions to the project pass basic build and install checks.

The target platforms are
1) PostgreSQL 9.6.
2) GPDB 4.3.x (later will be 5.x when released)


> Build process on Apache infrastructure
> --
>
> Key: MADLIB-920
> URL: https://issues.apache.org/jira/browse/MADLIB-920
> Project: Apache MADlib
>  Issue Type: Test
>  Components: Build System
>Reporter: Frank McQuillan
>Assignee: Rahul Iyer
> Fix For: v2.0
>
>
> As a MADlib developer, I would like to build a complete docker file + image 
> with instructions on how to start/build/test MADlib, so that community 
> developers can use this to test.  Please put the file in src code, put 
> instructions on wiki.
> We are doing this in part because access to Apache Build system for MADlib 
> gives access to all incubating projects, and we don't want to facilitate that.
> Needed for graduation to TLP.
> The target platforms are:
> 1) PostgreSQL 9.6
> 2) gpdb 4.3.x (later 5.x)
> Please indicate of gpdb part is taking a ton of time and if so, maybe we live 
> with PG for now.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MADLIB-1024) CREATE EXTENSION madlib fails

[Mauricio Scheffer (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867584#comment-15867584
 ] 

Mauricio Scheffer commented on MADLIB-1024:
---

My docker image is built on top of the official Postgres image, which uses 
Debian Jessie as the OS.
The image build log shows it installs libpython2.7 and if if run `python 
--version` it shows 2.7.9


> 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.10
>
> 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)