amoeba commented on issue #3449: URL: https://github.com/apache/arrow-adbc/issues/3449#issuecomment-3315409292
Separating the vendor and type into separate fields implies a processing rule like, > "If clients choose to process the `ADBC::typename` field, they **SHOULD** first check `ARROW::typename_vendor`... with really interesting behavior for clients that don't follow this rule. It seems good to try to avoid splitting this information up because it's not two separate pieces of information. However, one good reason I can come up with to separate the vendor+type tuple out into separate fields is if it's anticipated that there may be more vendor-specific information and we don't want to make clients repeat themselves. What about namespacing the type name in the value instead like `ADBC:typename = $VENDOR_$TYPE_NAME`? This implies its own processing rule but I like it better than `ADBC:$VENDOR:typename`. I'm just throwing that out there since I didn't see it mentioned yet. I'm fairly supportive of `ADBC:VENDOR:typename` too. -- 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]
