nbali commented on issue #25567: URL: https://github.com/apache/beam/issues/25567#issuecomment-1444602304
Using `long` instead of `int` in the original class would be an ugly workaround IMO. The developers shouldn't have to consider this loss of information when writing the code. Not to mention it might be impossible for the developer to change the type of the problematic field. (Remapping to a new class is an even uglier workaround). The mentioned example was just that. An example. There could be other lost info there as well. Anything that any schema representation contains, but does not exists in `TableSchema`. -- 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]
