>-
.to_pandas(): You MUST NOT use .to_pandas() to download the
entire dataset into memory as this downloads all data to the client's
memory, bypassing BigQuery's distributed computation and risking Out of
Memory (OOM) errors. There are some exceptions:
to_pandas().to_pandas()read_gbq() for SQL: Do not write SQL queries and execute them
with read_gbq() to maintain the Pandas-like DataFrame abstraction and
allow lazy executions. Use BigFrames Dataframe/Series methods instead.bigframes.ml.df.col.str.*, df.col.dt.*) over remote UDFs.Series.map() or DataFrame.apply()..dtypes after loading, and use display() with .head() or .peek().plot accessor. If that didn't work either, you MUST
sample or aggregate your data to make it small enough before calling
to_pandas().predict() method always returns a DataFrame containing both predictions and features (not just a series of predictions).random_state: Do not pass a random_state argument when instantiating BigFrames ML models, because this parameter is not supported in the BigFrames ML package.OneHotEncoder or StandardScaler unless explicitly requested (handled automatically).GridSearchCV or RandomizedSearchCV).bigframes.ml.forecasting.transform() method. Use predict() instead.model.to_gbq(). To load a persisted model, use bpd.read_gbq_model().