tickets/SP-3204-review-for-release - #185
Conversation
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
| @@ -0,0 +1,758 @@ | |||
| { | |||
There was a problem hiding this comment.
Be sure to update the link to point to DP2 docs (it's currently dp1).
Also, pipelines version should be r30.0.10.
Reply via ReviewNB
There was a problem hiding this comment.
Thanks for the catch.
There was a problem hiding this comment.
Also updating 201.XX to 201.15.
| @@ -0,0 +1,758 @@ | |||
| { | |||
There was a problem hiding this comment.
There was a problem hiding this comment.
Oops, thought I got all of these, but clearly missed some. Thanks!
| @@ -0,0 +1,758 @@ | |||
| { | |||
There was a problem hiding this comment.
| @@ -0,0 +1,758 @@ | |||
| { | |||
There was a problem hiding this comment.
| @@ -0,0 +1,758 @@ | |||
| { | |||
There was a problem hiding this comment.
Is there a need to retrieve the full table? You could use "SELECT TOP 10..." or something to demonstrate the query, and it would be much faster.
Reply via ReviewNB
| @@ -0,0 +1,648 @@ | |||
| { | |||
There was a problem hiding this comment.
| @@ -0,0 +1,648 @@ | |||
| { | |||
There was a problem hiding this comment.
| @@ -0,0 +1,648 @@ | |||
| { | |||
There was a problem hiding this comment.
Probably no need to get the entire table? Maybe use "SELECT TOP N...".
Also, "ORDER BY" probably makes this query much slower. I think sorting after returning results would be better (though maybe check our TAP tutorials for advice on this).
Reply via ReviewNB
There was a problem hiding this comment.
Same issue as for the current_identifications table with joins and the workaround provided here.
I tested the query both with and without the "ORDER BY" inclusion and the query time was the same, so I'll leave it as an example of how to order retrieved table info. I also don't know if ordering the two table queries that are merged later for the join workaround makes the dataframe merge faster?
| @@ -0,0 +1,648 @@ | |||
| { | |||
There was a problem hiding this comment.
| @@ -0,0 +1,648 @@ | |||
| { | |||
There was a problem hiding this comment.
See my comments on NB 201_15 about (a) returning the entire table from your query (is it needed?), (b) using pandas to join (could do it in the query), and (c) counting (can do via TAP).
I would rewrite this section with those changes in mind.
Reply via ReviewNB
There was a problem hiding this comment.
The workaround was included for the join issues for some SS tables. I think that means this should stay as is for now, and once a fix can be implemented for table joins, the tutorials can be updated, but if this should still be changed, let me know.
jeffcarlin
left a comment
There was a problem hiding this comment.
Left comments in ReviewNB. The main thing is that I think we should avoid queries that return full tables. Demonstrating to users how to query tables doesn't need the whole thing.
Add 201 series notebooks for
current_identificationsandnumbered_identificationstables.