feat: support array output in remote_function
#1057
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is feature request to support use cases like creating custom feature vectors, embeddings etc.
…tr array outputs
|
|
||
| # if the output is an array, reconstruct it from the json serialized | ||
| # string form | ||
| if bigframes.dtypes.is_array_like(func.output_dtype): |
Contributor
There was a problem hiding this comment.
Do we actually handle any array-like dtype?
Contributor
Author
There was a problem hiding this comment.
Um, in this PR we are looking to support types like list[int] on the output side? Or I didn't get you?
|
|
||
| # if the output is an array, reconstruct it from the json serialized | ||
| # string form | ||
| if bigframes.dtypes.is_array_like(func.output_dtype): |
Contributor
There was a problem hiding this comment.
seems the code within this block assume not just array_like, but specifically that it is a pyarrow list_ type
Contributor
Author
There was a problem hiding this comment.
That's exactly what the array_like implementation checks?
python-bigquery-dataframes/bigframes/dtypes.py
Lines 301 to 304 in 5a2731b
Contributor
There was a problem hiding this comment.
eh, probably fine then, I don't really see array_like definition expanding anytime soon
bigframes/functions/_utils.py
Outdated
| return None | ||
|
|
||
| try: | ||
| python_output_type = eval(output_type) |
Contributor
There was a problem hiding this comment.
eval always makes me a bit uncomfortable - can we do this in a more constrained way?
Contributor
Author
There was a problem hiding this comment.
removed eval in the latest patch, PTAL
bigframes/functions/_utils.py
Outdated
| if typing.get_origin(python_output_type) is list: | ||
| python_output_type_ser = repr(python_output_type) | ||
| else: | ||
| python_output_type_ser = python_output_type.__name__ |
Contributor
There was a problem hiding this comment.
shoudl we bother with non-list types right now?
Contributor
Author
There was a problem hiding this comment.
throwing error for non-array and not-supported-array types in the latest patch, PTAL
TrevorBergeron
approved these changes
Jan 15, 2025
shuoweil
pushed a commit
that referenced
this pull request
Jan 20, 2025
* feat: support array output in `remote_function` This is feature request to support use cases like creating custom feature vectors, embeddings etc. * add multiindex test * move array type conversion to bigquery module, test multiindex * add `bigframes.bigquery.json_extract_string_array`, support int and str array outputs * increase cleanup rate * update input and output types doc * support array output in DataFrame.apply * support read_gbq_function on a remote function created for array output * fix the json_set after variable renaming * add tests for output_type in read_gbq_function * temporarily exclude system 3.9 tests and include 3.10 and 3.11 * Revert "temporarily exclude system 3.9 tests and include 3.10 and 3.11" This reverts commit 2485aa3. * add more info in the unexpected exception * more debug info * use unique routine name across tests * Revert "more debug info" This reverts commit 86fe316. * Revert "add more info in the unexpected exception" This reverts commit fe010cb. * support array output in binary remote function operations * support array output in nary remote function operations * preserve array output type in function description to avoid explit output_type in read_gbq_function * fix one failing read_gbq_function test * make test parameterization order deterministic * fix sorting of types for mypy * remove test parameterization with sorting inside * include partial ordering mode testing for read_gbq_function * add remote function array out test in partial ordering mode * avoid repr-eval for output type serialization/deserialization * remove unsupported scenarios system tests, use common exception for unsupported
shuoweil
pushed a commit
that referenced
this pull request
Jan 20, 2025
* feat: support array output in `remote_function` This is feature request to support use cases like creating custom feature vectors, embeddings etc. * add multiindex test * move array type conversion to bigquery module, test multiindex * add `bigframes.bigquery.json_extract_string_array`, support int and str array outputs * increase cleanup rate * update input and output types doc * support array output in DataFrame.apply * support read_gbq_function on a remote function created for array output * fix the json_set after variable renaming * add tests for output_type in read_gbq_function * temporarily exclude system 3.9 tests and include 3.10 and 3.11 * Revert "temporarily exclude system 3.9 tests and include 3.10 and 3.11" This reverts commit 2485aa3. * add more info in the unexpected exception * more debug info * use unique routine name across tests * Revert "more debug info" This reverts commit 86fe316. * Revert "add more info in the unexpected exception" This reverts commit fe010cb. * support array output in binary remote function operations * support array output in nary remote function operations * preserve array output type in function description to avoid explit output_type in read_gbq_function * fix one failing read_gbq_function test * make test parameterization order deterministic * fix sorting of types for mypy * remove test parameterization with sorting inside * include partial ordering mode testing for read_gbq_function * add remote function array out test in partial ordering mode * avoid repr-eval for output type serialization/deserialization * remove unsupported scenarios system tests, use common exception for unsupported
shuoweil
pushed a commit
that referenced
this pull request
Jan 20, 2025
* feat: support array output in `remote_function` This is feature request to support use cases like creating custom feature vectors, embeddings etc. * add multiindex test * move array type conversion to bigquery module, test multiindex * add `bigframes.bigquery.json_extract_string_array`, support int and str array outputs * increase cleanup rate * update input and output types doc * support array output in DataFrame.apply * support read_gbq_function on a remote function created for array output * fix the json_set after variable renaming * add tests for output_type in read_gbq_function * temporarily exclude system 3.9 tests and include 3.10 and 3.11 * Revert "temporarily exclude system 3.9 tests and include 3.10 and 3.11" This reverts commit 2485aa3. * add more info in the unexpected exception * more debug info * use unique routine name across tests * Revert "more debug info" This reverts commit 86fe316. * Revert "add more info in the unexpected exception" This reverts commit fe010cb. * support array output in binary remote function operations * support array output in nary remote function operations * preserve array output type in function description to avoid explit output_type in read_gbq_function * fix one failing read_gbq_function test * make test parameterization order deterministic * fix sorting of types for mypy * remove test parameterization with sorting inside * include partial ordering mode testing for read_gbq_function * add remote function array out test in partial ordering mode * avoid repr-eval for output type serialization/deserialization * remove unsupported scenarios system tests, use common exception for unsupported
shuoweil
pushed a commit
that referenced
this pull request
Jan 20, 2025
* feat: support array output in `remote_function` This is feature request to support use cases like creating custom feature vectors, embeddings etc. * add multiindex test * move array type conversion to bigquery module, test multiindex * add `bigframes.bigquery.json_extract_string_array`, support int and str array outputs * increase cleanup rate * update input and output types doc * support array output in DataFrame.apply * support read_gbq_function on a remote function created for array output * fix the json_set after variable renaming * add tests for output_type in read_gbq_function * temporarily exclude system 3.9 tests and include 3.10 and 3.11 * Revert "temporarily exclude system 3.9 tests and include 3.10 and 3.11" This reverts commit 2485aa3. * add more info in the unexpected exception * more debug info * use unique routine name across tests * Revert "more debug info" This reverts commit 86fe316. * Revert "add more info in the unexpected exception" This reverts commit fe010cb. * support array output in binary remote function operations * support array output in nary remote function operations * preserve array output type in function description to avoid explit output_type in read_gbq_function * fix one failing read_gbq_function test * make test parameterization order deterministic * fix sorting of types for mypy * remove test parameterization with sorting inside * include partial ordering mode testing for read_gbq_function * add remote function array out test in partial ordering mode * avoid repr-eval for output type serialization/deserialization * remove unsupported scenarios system tests, use common exception for unsupported
shuoweil
pushed a commit
that referenced
this pull request
Jan 24, 2025
* feat: support array output in `remote_function` This is feature request to support use cases like creating custom feature vectors, embeddings etc. * add multiindex test * move array type conversion to bigquery module, test multiindex * add `bigframes.bigquery.json_extract_string_array`, support int and str array outputs * increase cleanup rate * update input and output types doc * support array output in DataFrame.apply * support read_gbq_function on a remote function created for array output * fix the json_set after variable renaming * add tests for output_type in read_gbq_function * temporarily exclude system 3.9 tests and include 3.10 and 3.11 * Revert "temporarily exclude system 3.9 tests and include 3.10 and 3.11" This reverts commit 2485aa3. * add more info in the unexpected exception * more debug info * use unique routine name across tests * Revert "more debug info" This reverts commit 86fe316. * Revert "add more info in the unexpected exception" This reverts commit fe010cb. * support array output in binary remote function operations * support array output in nary remote function operations * preserve array output type in function description to avoid explit output_type in read_gbq_function * fix one failing read_gbq_function test * make test parameterization order deterministic * fix sorting of types for mypy * remove test parameterization with sorting inside * include partial ordering mode testing for read_gbq_function * add remote function array out test in partial ordering mode * avoid repr-eval for output type serialization/deserialization * remove unsupported scenarios system tests, use common exception for unsupported
shuoweil
pushed a commit
that referenced
this pull request
Jan 24, 2025
* feat: support array output in `remote_function` This is feature request to support use cases like creating custom feature vectors, embeddings etc. * add multiindex test * move array type conversion to bigquery module, test multiindex * add `bigframes.bigquery.json_extract_string_array`, support int and str array outputs * increase cleanup rate * update input and output types doc * support array output in DataFrame.apply * support read_gbq_function on a remote function created for array output * fix the json_set after variable renaming * add tests for output_type in read_gbq_function * temporarily exclude system 3.9 tests and include 3.10 and 3.11 * Revert "temporarily exclude system 3.9 tests and include 3.10 and 3.11" This reverts commit 2485aa3. * add more info in the unexpected exception * more debug info * use unique routine name across tests * Revert "more debug info" This reverts commit 86fe316. * Revert "add more info in the unexpected exception" This reverts commit fe010cb. * support array output in binary remote function operations * support array output in nary remote function operations * preserve array output type in function description to avoid explit output_type in read_gbq_function * fix one failing read_gbq_function test * make test parameterization order deterministic * fix sorting of types for mypy * remove test parameterization with sorting inside * include partial ordering mode testing for read_gbq_function * add remote function array out test in partial ordering mode * avoid repr-eval for output type serialization/deserialization * remove unsupported scenarios system tests, use common exception for unsupported
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull req
2C47
uest is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
remote_function: screen/5rMtCZVaUYKdqxPSeries.apply: screen/9HkKMuWxMvbbPgfDataFrame.apply: screen/BoXH9A7d4hGpETuFixes internal issue 298876217 🦕