feat: Shimmed RowSet and RowRange for ReadRows.#1296
feat: Shimmed RowSet and RowRange for ReadRows.#1296gkevinzheng wants to merge 1 commit intomutate-rowsfrom
Conversation
Summary of ChangesHello @gkevinzheng, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces significant refactoring to align the legacy Bigtable client's Highlights
Changelog
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request refactors RowSet and RowRange to act as shims over new data client classes, which is a solid improvement for maintainability. Moving _MappableAttributesMixin to a shared helper file is also a good refactoring. I've identified one critical bug that would cause a runtime error and another medium-severity issue related to encapsulation that could be improved.
| return { | ||
| descriptor.name: value for descriptor, value in self._pb._pb.ListFields() | ||
| } |
There was a problem hiding this comment.
There seems to be a typo here. self._pb is the protobuf message object, which has the ListFields() method. Accessing self._pb._pb will result in an AttributeError because the protobuf message object does not have a _pb attribute.
| return { | |
| descriptor.name: value for descriptor, value in self._pb._pb.ListFields() | |
| } | |
| return { | |
| descriptor.name: value for descriptor, value in self._pb.ListFields() | |
| } |
| for each in self._read_rows_query._row_set.row_keys: | ||
| message.rows.row_keys._pb.append(_to_bytes(each)) | ||
|
|
||
| for each in self.row_ranges: | ||
| r_kwrags = each.get_range_kwargs() | ||
| message.rows.row_ranges.append(r_kwrags) | ||
| for each in self._read_rows_query._row_set.row_ranges: | ||
| message.rows.row_ranges.append(each) |
There was a problem hiding this comment.
Accessing the private attribute _row_set of _read_rows_query breaks encapsulation and makes this code brittle to future changes in the ReadRowsQuery class. It's better to use the public properties row_keys and row_ranges. While this might involve a small performance cost due to object wrapping and unwrapping for ranges, it ensures better code maintainability.
| for each in self._read_rows_query._row_set.row_keys: | |
| message.rows.row_keys._pb.append(_to_bytes(each)) | |
| for each in self.row_ranges: | |
| r_kwrags = each.get_range_kwargs() | |
| message.rows.row_ranges.append(r_kwrags) | |
| for each in self._read_rows_query._row_set.row_ranges: | |
| message.rows.row_ranges.append(each) | |
| for each in self._read_rows_query.row_keys: | |
| message.rows.row_keys._pb.append(_to_bytes(each)) | |
| for each in self._read_rows_query.row_ranges: | |
| message.rows.row_ranges.append(each._to_pb()) |
Changes made:
_MappableAttributesMixintohelpers.pyfor use inRowRange.RowRangeandReadRowsQueryfrom the data client as backing data sources forRowRangeandRowSetrespectively.