laserninja commented on issue #12594: URL: https://github.com/apache/gravitino/issues/12594#issuecomment-5944902157
Added the regression coverage in #13512 and resolved its conflicts with main. Source validation now also runs before `replaceDefinition` is dispatched. All 605 server tests pass. The HTTP tests found a distinction: - Whitespace-only catalog names are rejected before lookup (`Metadata object full name cannot be blank`), even with authorization disabled. - Missing sources with whitespace-only schema/table names are rejected before persistence. - Whitespace-only schema/table names pass if the mocked connector resolves the source, for both create and replacement, with authorization enabled or disabled. The 24-case matrix captures these results without introducing a new naming rule. The resolver is mocked, so this is evidence of the native validation behavior, not a claim that every external catalog supports such names. For the resolvable schema/table case, should native writes reject blank source segments, or should Ossie support quoted whitespace-only segments? I have left that policy unchanged pending agreement so we can align both paths consistently. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
