You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Came across this by accident where I assumed a DataFrame was a Pandas DataFrame and I wanted to convert to a H2O DataFrame. But, since it was already a H2O DataFrame it failed instead.
precising expected behaviour: the wrapped frame should share same data with the original one, but have a different id, this means that they are represented by different objects on the backend—we explicitely created a new frame using the Py client after all—, even if they may share the data content (no deep cloning).
#15898)
* generates a shallow copy when Py H2OFrame constructor is called with an existing H2OFrame
* add support for columns selection params
* added proper tests for H2OFrame constructor and discovered a bunch of bugs…
* cosmetics
* added references to new issues discovered when writing H2OFrame tests
Came across this by accident where I assumed a DataFrame was a Pandas DataFrame and I wanted to convert to a H2O DataFrame. But, since it was already a H2O DataFrame it failed instead.
Actual behavior
Expected behavior
Converting a Pandas DataFrame, to a H2O DataFrame.
The following code snippet should work too without throwing an error.
The text was updated successfully, but these errors were encountered: