brettbuddin commented on PR #33983: URL: https://github.com/apache/arrow/pull/33983#issuecomment-1420032159
@zeroshade After working the problem a bit I wasn't able to come up with a solution where augmenting the Flight server gave me what I needed. To me, it's more clear to separate the creation of the database from the gRPC service—making a dependency relationship. In `main.go` this results in the ability to just `defer` closure for when the server is completely out of the way, and in tests we just articulate closure in the suite's test teardown. The consequence is an added step in creation of the server. Given my experience with this example: the point is to provide a binary to use in integration testing. It's not so important to me how many steps it takes to create that gRPC service layer. Thoughts? -- 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]
