…dmin client, not the handwritten layer (#1697)

* Export the GCRuleMaker class

* Use the admin client for the first sample

* feat: updated samples to use GCRuleMaker

* feat: updated samples to use GCRuleMaker

* feat: Update restoreTable sample to use generated client

This commit updates the `backups.restore.js` sample to use the `BigtableTableAdminClient` directly for restoring a table from a backup, instead of going through the handwritten `bigtable.instance().createTableFromBackup()` method.

This change is based on the design document for the Node.js Bigtable Admin API autogeneration.

The corresponding test for the sample in `samples/test/backups.js` has also been updated to pass the correct arguments to the updated sample script.

* table id to table name

* The rule should be a union - not nested

instance of the admin client should be used

* Use instance of admin client - not admin client

itself

* Update the rules so they won’t throw errors

* change family.id to family.name

* max age has to be at least 1 millisecond

* Run linter

* Refresh project id token

* Get rid of projectId token

* revert change to backups method called

* Use the admin client for createTable instead

* snippets should include admin client

* This code snippet should include project fetch

* Comment out options

* Use the admin client to create a table

* Use the generated layer for maxVersions

* Don’t use instance.name in parent path

* Update the family snippets

* Update createTable in the Row samples

* Eliminate the need for any default projectId fetch

* Don’t hardcode the project id

* don’t hardcode project id

* commit examples

* Don’t create table twice

* options is not used. remove it

* table admin

* Hardcode instance name

* delete the examples folder

* remove options

* add header

---------

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

…o use the generated layer instead (#1710)

* Export the GCRuleMaker class

* Use the admin client for the first sample

* feat: updated samples to use GCRuleMaker

* feat: updated samples to use GCRuleMaker

* feat: Update restoreTable sample to use generated client

This commit updates the `backups.restore.js` sample to use the `BigtableTableAdminClient` directly for restoring a table from a backup, instead of going through the handwritten `bigtable.instance().createTableFromBackup()` method.

This change is based on the design document for the Node.js Bigtable Admin API autogeneration.

The corresponding test for the sample in `samples/test/backups.js` has also been updated to pass the correct arguments to the updated sample script.

* table id to table name

* The rule should be a union - not nested

instance of the admin client should be used

* Use instance of admin client - not admin client

itself

* Update the rules so they won’t throw errors

* change family.id to family.name

* max age has to be at least 1 millisecond

* Run linter

* Refresh project id token

* Get rid of projectId token

* revert change to backups method called

* Use the admin client for createTable instead

* snippets should include admin client

* This code snippet should include project fetch

* Comment out options

* Use the admin client to create a table

* Use the generated layer for maxVersions

* Don’t use instance.name in parent path

* Update the family snippets

* Update createTable in the Row samples

* Eliminate the need for any default projectId fetch

* Don’t hardcode the project id

* don’t hardcode project id

* commit examples

* Don’t create table twice

* options is not used. remove it

* table admin

* Hardcode instance name

* delete the examples folder

* remove options

* add header

* The rest of the samples should use

BigtableTableAdminClient instread

* Update more tables code

* commit the api-reference-doc-snippets

* correct the backups samples

* Revert "correct the backups samples"

This reverts commit 7241dbe.

* Modify the reads samples

* Update the functions script

* Make separate column family creation calls

This makes the test pass

* Fix the deletes sample changes

* change the fixture

don’t wrap the return value in brackets

* return value should be false literal

* Correct the fixture for the deletes samples

* Reintroduce the backup samples

* Replace write.js code with calls to generated layr

* removed unused table

* backups from instance as well

* Fix the index.js sample

* Fixed a bunch of syntax highlighting errors

* run the linter

* Changes to pass the linting check

* Eliminate unused cluster

* Add comment for restore table LRO

* Add a script for the consistency token

* Update the restore table snippet

* Setup the polling harness for optimized restore tb

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

* update snippets - optimization

* Correct header

* Add code that makes the optimized restore table

call

---------

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

…o avoid segfault (#1715)

🤖 I have created a release *beep* *boop*
---


## [6.4.1](https://togithub.com/googleapis/nodejs-bigtable/compare/v6.4.0...v6.4.1) (2025-09-09)


### Bug Fixes

* Directly import JS-native impl for crc32c on non-x64 platforms to avoid segfault ([#1715](https://togithub.com/googleapis/nodejs-bigtable/issues/1715)) ([9848963](https://togithub.com/googleapis/nodejs-bigtable/commit/98489637befe779df0438f466eecb0428222a29a))

---
This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).