Fix registration in publisher, handle data_type attribute in Channel better

Not sure why/how the properties handling in registration wasn't an issue before, perhaps the Flight API had changed, but this fixes an issue where the resulting data from a publish request wasn't being unpacked into the properties dict properly.

Also in the process, the publish example in the README had an issue where the metadata accepted in Channels did not accept raw numpy types well, as they do not have the name attribute. Forcing a cast within the Channel class handles this well, since converting a raw numpy type gives a numpy.dtype object, but converting an already existing numpy.dtype object is a no-op.

requested review from @jameson.rollins

@patrick.godwin for future reference, it would be nice if the commit messages gave a little more info about why the change was needed. So for instance, the second commit log says that it fixes an issue, but it doesn't say what the issue was exactly.

But that's a minor point, so I'll approve.

That's a very good point. I can reword the commit real quick so it's more clear and then merge this.

approved this merge request

added 1 commit

• 6b7ac615 - fix issue in parsing properties from record batch in client registration

Compare with previous version

mentioned in commit 7092c6a9

merged