[GitHub] madlib issue #292: Internal: Add function to check column type for 1D array

[asfgit]

Github user asfgit commented on the issue:

https://github.com/apache/madlib/pull/292
  

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/madlib-pr-build/558/



---

[GitHub] madlib issue #291: Feature: Vector to Columns

[asfgit]

Github user asfgit commented on the issue:

https://github.com/apache/madlib/pull/291
  

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/madlib-pr-build/556/



---

[GitHub] madlib issue #292: Internal: Add function to check column type for 1D array

[ArvindSridhar]

Github user ArvindSridhar commented on the issue:

https://github.com/apache/madlib/pull/292
  
Sounds good. Just pushed a commit to this PR, will rebase and add back the 
original function to the original vec2cols PR tomorrow


---

[GitHub] madlib issue #292: Internal: Add function to check column type for 1D array

[iyerr3]

Github user iyerr3 commented on the issue:

https://github.com/apache/madlib/pull/292
  
Yeah, the unit tests are unnecessary after this change. I vote to remove
them, with just the function added back to the original PR.



On Thu, Jul 12, 2018 at 5:26 PM Arvind Sridhar 
wrote:

> Sounds good-just verified that plpy converts the SQL bool into a Python
> bool and not a Python string. It should be good to go now. Do we still 
want
> to get rid of the unit tests now given that they would be almost trivial
> (basically just checking that True=True)?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> , or 
mute
> the thread
> 

> .
>



---

[GitHub] madlib issue #292: Internal: Add function to check column type for 1D array

[ArvindSridhar]

Github user ArvindSridhar commented on the issue:

https://github.com/apache/madlib/pull/292
  
Sounds good-just verified that plpy converts the SQL bool into a Python 
bool and not a Python string. It should be good to go now. Do we still want to 
get rid of the unit tests now given that they would be almost trivial 
(basically just checking that True=True)?


---

[GitHub] madlib issue #290: madpack: Add madpack option to run unit tests.

[asfgit]

Github user asfgit commented on the issue:

https://github.com/apache/madlib/pull/290
  

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/madlib-pr-build/555/



---

[GitHub] madlib issue #292: Internal: Add function to check column type for 1D array

[iyerr3]

Github user iyerr3 commented on the issue:

https://github.com/apache/madlib/pull/292
  
That's a valid concern. You could return bool(result[0]['n_y']) to ensure a
bool output instead of a string (though I believe the SPI ensures that
boolean from SQL is returned as bool in Python).

>



---

[GitHub] madlib pull request #287: Fix incorrect dict expansion in table header

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/madlib/pull/287


---

[GitHub] madlib pull request #286: Build: Remove symlinks during rpm uninstall

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/madlib/pull/286


---

[GitHub] madlib pull request #293: Utilities: Add check for whether type is of any ar...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/madlib/pull/293


---

[GitHub] madlib issue #292: Internal: Add function to check column type for 1D array

[iyerr3]

Github user iyerr3 commented on the issue:

https://github.com/apache/madlib/pull/292
  
Few comments: 
1. The query would read better if it is setup to return a boolean i.e. 
using `array_upper(..., 2) IS NULL` instead of converting the integer output to 
bool in Python. 
2. My request in #291 for moving this to a separate commit was for the 
`plpy_mock.py_in` file since that looks like an independent work. This function 
is minor enough that it can be kept in #291. 
3. The unit test for this function isn't really testing anything except the 
last line in the function. That also becomes moot if comment 1. is accepted. 
Considering this, I suggest we don't have the unit test for this function (at 
least not in the form it currently is). 


---

[GitHub] madlib issue #292: Internal: Add function to check column type for 1D array

[asfgit]

Github user asfgit commented on the issue:

https://github.com/apache/madlib/pull/292
  

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/madlib-pr-build/554/



---

[GitHub] madlib issue #292: Internal: Add function to check column type for 1D array

[asfgit]

Github user asfgit commented on the issue:

https://github.com/apache/madlib/pull/292
  

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/madlib-pr-build/553/



---

[GitHub] madlib issue #293: Utilities: Add check for whether type is of any array var...

[asfgit]

Github user asfgit commented on the issue:

https://github.com/apache/madlib/pull/293
  

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/madlib-pr-build/552/



---

[GitHub] madlib pull request #291: Feature: Vector to Columns

[ArvindSridhar]

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

https://github.com/apache/madlib/pull/291#discussion_r202140243
  
--- Diff: 
src/ports/postgres/modules/utilities/test/unit_tests/test_utilities.py_in ---
@@ -243,6 +243,9 @@ class UtilitiesTestCase(unittest.TestCase):
 self.assertFalse(s.is_valid_psql_type('boolean[]', s.INCLUDE_ARRAY 
| s.ONLY_ARRAY))
 self.assertFalse(s.is_valid_psql_type('boolean', s.ONLY_ARRAY))
 self.assertFalse(s.is_valid_psql_type('boolean[]', s.ONLY_ARRAY))
+self.assertTrue(s.is_valid_psql_type('boolean[]', s.ANY_ARRAY))
--- End diff --

Done, should be on PRs 292 and 293


---

[GitHub] madlib pull request #292: Internal: Add function to check column type for 1D...

[ArvindSridhar]

GitHub user ArvindSridhar opened a pull request:

https://github.com/apache/madlib/pull/292

Internal: Add function to check column type for 1D array

Added a db_utils function to check whether a column of type array contains 
1D arrays only

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

$ git pull https://github.com/madlib/madlib chore/check-col-type

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

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


commit 4e29d202dbd03859167a074fe807a3c50ec93ad1
Author: Arvind Sridhar 
Date:   2018-07-09T23:12:28Z

Internal: Add function to check column type for 1D array

Co-authored-by: Nikhil Kak 




---

[GitHub] madlib issue #291: Feature: Vector to Columns

[asfgit]

Github user asfgit commented on the issue:

https://github.com/apache/madlib/pull/291
  

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/madlib-pr-build/551/



---

[GitHub] madlib issue #291: Feature: Vector to Columns

[fmcquillan99]

Github user fmcquillan99 commented on the issue:

https://github.com/apache/madlib/pull/291
  
user docs seem incomplete


---

[GitHub] madlib pull request #282: Utilites: Add CTAS while dropping some columns

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/madlib/pull/282


---

[GitHub] madlib issue #290: madpack: Add madpack option to run unit tests.

[njayaram2]

Github user njayaram2 commented on the issue:

https://github.com/apache/madlib/pull/290
  
Thank you for the comments @iyerr3 , will do the needful.


---

[GitHub] madlib issue #282: Utilites: Add CTAS while dropping some columns

[fmcquillan99]

Github user fmcquillan99 commented on the issue:

https://github.com/apache/madlib/pull/282
  
ah, i see.  I think it is fine as you have put it.

LGTM


---