Answers to frequently asked questions about FeatureStore, including authorization errors, data source configuration issues, and data synchronization.
Q: What do I do if the prompt Make sure that you complete authorization before you create a Hologres data store appears when creating a Hologres data store?
Example
Causes:
Possible causes:
The RAM user using FeatureStore is not authorized to use the Hologres instance.
The RAM user using FeatureStore is not authorized to use the corresponding Hologres database.
The Hologres instance version is lower than 2.0.18
Solutions:
Log on to the Hologres Console.
In the left-side navigation bar, click Instances.
Click the name of the instance to go to the instance details page.
Click Account Management.
On the User Management page, click Add User in the upper right corner.
Select the RAM user using FeatureStore. Then, select Examples of the Super Administrator (SuperUser) or Regular User, and click OK.
If the user is granted the Regular User permissions, you need to grant the permission to access the corresponding database.
Go to the instance details page.
Click Database Management.
On the Database Authorization page, click Authorize User in the Actions column of the database.
Click Grant Permissions in the upper right corner.
Select the RAM user using FeatureStore and set it as a Developer. Then, click OK.
If the problem persists, check whether the Hologres instance version is lower than 2.0.18. If so, upgrade the instance to the latest version.
Q: What do I do if the prompt indicating that PrivateLink is not activated when I configure VPC direct connection during the creation of a FeatureDB data source?
Causes:
VPC direct connection relies on PrivateLink, which is not activated.
Solutions:
Click Activate Now on the prompt page, or activate PrivateLink by following the instructions in Access Alibaba Cloud services.
Q: What do I do if the error "Access denied by project vpc white list: vpc:'vpc-xxx' not in vpc white list, ip: 'xxxx'. project: xxx" appears when I perform a MaxCompute-related operation?
Example:
Causes:
The MaxCompute project has the whitelist feature enabled, and the VPC ID of FeatureStore is not added to the whitelist.
Solutions:
Log on the MaxCompute console.
In the left-side navigation pane, choose Workspace > Projects.
Click Manage to the right of the target to access the project details page.
In the IP Address Whitelist section of the Parameter Configuration tab, click Edit.
Add the VPC ID of FeatureStore to the VPC IP Address editor. For more information, see Manage IP address whitelists. The following table lists the VPC IDs by region.
Region
VPC ID
China (Hangzhou)
vpc-bp1vacu28qkj1fv6zpkq1
China (Shanghai)
vpc-uf6rcto3hlh9wjkgcqfbf
China (Beijing)
vpc-2zexf99g0maxm8jgx3se0
China (Shenzhen)
vpc-wz96kdcavm40pi6158ibd
China (Hong Kong)
vpc-j6cr1dmfkjuhu5cz61cl7
Singapore
vpc-t4nflw68k7pitfq0oe0oh
US (Silicon Valley)
vpc-rj9suctodeems1xwk6xo9
US (Virginia)
vpc-0xitg4loq1mi9bjb57em7
Q: What do I do if the error password authentication failed for user "paifsslr$STS.**********" appears when creating a feature view?
Example:
password authentication failed for user "paifsslr$STS.**********"
Causes:
The RAM user using FeatureStore is not authorized to use the Hologres instance.
Solutions:
Authorize the RAM user to use the Hologres instance. For more information, see Create a data store.
Log on to the Hologres Console.
In the left-side navigation bar, click Instances.
Click the name of the instance to go to the instance details page.
Click Account Management.
On the User Management page, click Add User in the upper right corner.
Select the RAM user using FeatureStore. Then, select Examples of the Super Administrator (SuperUser) or Regular User, and click OK
(Optional) If the user is granted the Regular User permissions, you need to grant the permission to access the corresponding database.
Go to the instance details page.
Click Database Management.
On the Database Authorization page, click Authorize User in the Actions column of the database.
Click Grant Permissions in the upper right corner.
Select the RAM user using FeatureStore and set it as a Developer. Then, click OK.
(Optional) If the error persists, check whether the RAM user is granted the AliyunHologresFullAccess permission and upgrade the Hologres instance to the latest version.
Q: What do I do if the dial tcp: lookup hgpostcn-cn-xxx-cn-xxx.hologres.aliyuncs.com on 192.xxx.x.xx:xx: no such host error appears when creating a feature view?
Example:
Causes:
Possible causes:
Public network access is not enabled for the Hologres instance.
The Hologres instance is not running. For example, the instance may have expired.
Solutions:
Log on to the Hologres Console and check whether the Hologres instance is available.
Enable public network access.
In the left-side navigation bar, click Instances.
Click the name of the instance to go to the instance details page.
In the Network Information section, enable Public Network.
Perform one of the following operations based on the status of the instance.
If the instance has expired, renew the instance and try again. For more information, see Renewal management.
If the instance has been released, create a new Hologres instance first. Then, create a Hologres data store in FeatureStore or update the original data store.
If you create a new Hologres data store, you need to create a new FeatureStore project.
If you update the original Hologres data store, you can continue using the original FeatureStore project, but the previously created feature views and the associated model features are no longer available. You can delete them if you want to.
Q: What do I do if the Connect to FE failed,permission denied for database "ttx" error appears when creating a feature view?
Example:
Causes:
The RAM user is not authorized to access the Hologres database.
Solutions:
Grant the RAM user access to the Hologres database. For more information, see Create a data store.
Log on to the Hologres Console.
In the left-side navigation bar, click Instances.
Click the name of the instance to go to the instance details page.
Click Database Management.
On the Database Authorization page, click Authorize User in the Actions column of the database.
Click Grant Permissions in the upper right corner.
Select the RAM user using FeatureStore and set it as a Developer. Then, click OK.
Q: What do I do if the error "ODPS-0110061: Failed to run ddltask - xxxx. ExceptionBase: Schema evolution DDLs is not enabled in current project:xxxx" appears when I delete the feature field during model feature modification?
Example:
Causes:
Deleting a feature field requires deleting the corresponding field from the MaxCompute table. The current MaxCompute project does not have schema evolution enabled.
Solutions:
Run the setproject odps.schema.evolution.enable=true; command as described in error 1: Schema evolution DDLs is not enabled in current project:xxxx to enable schema evolution. Then, delete the model feature field after 10 minutes.
Q: How do I push offline feature data to an online data store?
To push data from a single partition, use the data synchronization feature on the Feature View page:
On the Feature View tab of the Project Details page, click Data Synchronization in the Actions column.
Specify the partition information.
Click Submit and the Synchronization History tab appears, where you can view the status of the data synchronization task.
To schedule daily data synchronization, take the following steps:
On the Feature View tab of the Project Details page, click Data Synchronization in the Actions column.
Copy the code from the Synchronize Code field.
Log on to the DataWorks Console. In the left-side navigation bar, click Data Development and O&M > Data Development.
Select the DataWorks workspace, and click Go to Data Development.
Move the pointer over Create, and choose Create Node > MaxCompute > PyODPS 3.
Copy the code in the Synchronize Code box to the code editor.
Click Properties on the right side of the tab. In the Properties panel, configure the scheduling parameters listed in the following table.
Parameter
Recommended value
Scheduling Parameter
Parameter Name
dt
Parameter Value
$[yyyymmdd-1]
Resource Group
Resource Group
Select the created exclusive resource group.
Dependencies
Select the offline table corresponding to the Feature View.
After the node is configured and tested, save and submit the node configurations.
Backfill data for the node. For more information, see Manage recommendation features with FeatureStore.
Q: What do I do if a permission error occurs when I execute the FeatureStore synchronization script in DataWorks?
Example:
File "/home/tops/lib/python3.7/site-packages/alibabacloud_tea_openapi/client.py", line 1442, in do_request
'accessDeniedDetail': self.default_any(err.get('AccessDeniedDetail'), err.get('accessDeniedDetail'))
Tea.exceptions.TeaException: Error: Forbidden.NoPermission code: 403, You are not authorized to do this operation. Action: featurestore:ListInstances;Resource: acs:featurestore:cn-beijing:${ID of the Alibaba Cloud account}:* request id: 2AF6CF28-B894-5119-A677-BE619341F497 Response: {'AccessDeniedDetail': {'AuthAction': 'featurestore:ListInstances', 'AuthPrincipalType': 'SubUser', 'AuthPrincipalOwnerId': '${ID of the Alibaba Cloud account}', 'AuthPrincipalDisplayName': '209226141687598727', 'PolicyType': 'AccountLevelIdentityBasedPolicy', 'NoPermissionType': 'ImplicitDeny', 'EncodedDiagnosticMessage': 'AQIBIAAAAL8VAcX2cL53ePOizTgZi1FjVPkvSaVAboCEz5/mWLB1TroSzqYluVa53zz3f2VofgxTvAqluAbsNlHJLh2LY9hxZ2m2Tbgao7wG3UHuIAge+n5OQ1vnlXMfEnczOSNze1BlHPsJBeDCJhIVym8u2NYoZkc4e1lRBfkArMdn6eay/M/D7YQLq42wXYB6fHVX+Y9qfaEG/rCZp/hQP/i0N9RxJzo3Kw4QHldejzmKuS9yZ7hlC79F/gbRpWi5OIDtUg3aabg115MrQg+TeNmwpBYMcp72GpfVxnQrKY5cydFm9TBuz0Z8uR6NemuKQAB3JSa+7UcjNu/Aqvyx83eYjc3Cr+E90qzfx9OSfv6xW/5rPBhm8fKLHbh4t3iJ8MUyrTfCiawCt5P1vO9Kl4IIJu8ksq+kpI1fof4re9vmoIEVQV8H/hQE8mjLFzaiWXgmjLP4AWMaFXzorh1JWhZsR9SDQvdluq/gP/HvFmBcdq8bqfGUNZ8X4hbLFYB1Nl/DmpRfPwAt4TZDtDSkDnDJg8537a232h6bN9s4v+G7WFDhZIC6oyUvm+WhKlptwhk5K7FQgtMkRe89rkWuD+N3jR8n2cQQHCeMrXZUQAPJybsfluPhKyBzY7sku4QLihK0vtO2sUCqvoCYHg27gjOod2egn6bv2TKNlkErkCyIfwbYmw+ljBjlX8ntmUbJPA973luCKzETWuI3hzIyeWk7JE9hFPUwZGV4lmUcXtfhnRaLAghqwTdszAIQ0Z8DwVs+8PcF3D7lFMYSbF+2zKw30dQ='}, 'RequestId': '2AF6CF28-B894-5119-A677-BE619341F497', 'Message': 'You are not authorized to do this operation. Action: featurestore:ListInstances;Resource: acs:featurestore:cn-beijing:${ID of the Alibaba Cloud account}:*', 'Recommend': 'https://api.aliyun.com/troubleshoot?q=Forbidden.NoPermission&product=PaiFeatureStore&requestId=2AF6CF28-B894-5119-A677-BE619341F497', 'HostId': 'paifeaturestore-vpc.cn-beijing.aliyuncs.com', 'Code': 'Forbidden.NoPermission', 'statusCode': 403}Causes:
When the FeatureStore synchronization script or export script runs in DataWorks, it uses temporarily generated AccessKey credentials. If the DataWorks account does not have FeatureStore permissions, these temporary credentials also lack the required permissions, causing the error.
Solutions:
Log on to the DataWorks console. In the left-side navigation pane, click Workspace. On the Workspaces page, find the desired workspace and click Manage in the Actions column.
In the left-side navigation pane, click Data Sources. Then, find the default MaxCompute data source associated with DataWorks and click Modify in the Operation column to view the default access identity (the account used to run DataWorks).
Attach the AliyunPAIFeatureStoreFullAccess policy to the corresponding account.
Alibaba Cloud account: When you activate PAI, the Alibaba Cloud account is automatically granted the required permissions.
RAM user: Use the Alibaba Cloud account to grant the RAM user the permissions.
Ensure that the associated cloud services, such as MaxCompute, DataWorks, and Hologres, have the permissions on FeatureStore.
(Optional) Add the VPC ID of FeatureStore to the whitelist of the associated cloud service.
If a cloud service does not have a whitelist configured, skip this step.
If an associated cloud service such as MaxCompute has a whitelist configured, add the VPC ID of FeatureStore to the whitelist.
Region
VPC ID
cn-beijing
vpc-2zexf99g0maxm8jgx3se0
cn-hangzhou
vpc-bp1vacu28qkj1fv6zpkq1
cn-shanghai
vpc-uf6rcto3hlh9wjkgcqfbf
cn-shenzhen
vpc-wz96kdcavm40pi6158ibd
cn-hongkong
vpc-j6cr1dmfkjuhu5cz61cl7