Hi, I am facing the following exception while uplo...
# troubleshooting
j
Hi, I am facing the following exception while uploading segments to an offline table
Copy code
Exception while uploading segment: Caught exception while updating ideal state for resource: SegmentMembershipTenant1_OFFLINE" while sending request: <http://localhost:9000/v2/segments?tableName=SegmentMembershipTenant1&tableName=SegmentMembershipTenant1&tableType=OFFLINE> to controller: 015461a2f6ba
Attaching the job spec and table configs for reference.
m
Do you have exception stack trace
j
I somehow created a table whose name is not similar to the name of the schema. When I dropped the table and tried to recreate it, it was throwing that names are not same. So I changed the names and recreated the tables. Then the segment upload was working properly. Why is there such a constraint that the table name and schema name should be same?
m
I don’t believe that the table and schema name need to match, there isn’t such a constraint. If you have the exact error I can take a look at the code
Hi Mayank bringing this back to your notice ☝️
👀 1
m
@John Peter S,so this was allowed originally. But this flexibility has been a root cause of a lot of user errors, due to which this validation check was added.
j
Okay 👍