Prateek Rungta

Dupe of #6

Ran into this while doing something today, [1](http://apache-spark-user-list.1001560.n3.nabble.com/Kryo-fails-with-avro-having-Arrays-and-unions-but-succeeds-with-simple-avro-td14549.html) & [2](https://github.com/bigdatagenomics/adam/blob/master/adam-core/src/main/scala/org/bdgenomics/adam/serialization/ADAMKryoRegistrator.scala) discuss the issue and solution well.

Would there be any interest in supporting a change to make pooling possible?

Hey @swapnilushinde, @rdblue: A few comments about this approach - a) I really like the `glob` idea. I think it solves a definite use-case and should stay in there. b)...

@swapnilushinde Ideally, I'd say we don't commit any of the stuff where we know we are going to change the interface on the cli, I think that means we would...

tl;dr - you should still be able to create tagged metrics with `NoopScope`/`TestScope`. E.g. test demonstrating this: ``` func TestExistingNoopAndTestScopeScope(t *testing.T) { scopes := []tally.Scope{ tally.NoopScope, tally.NewTestScope("", nil), } for...

@yutongp why do you want to migrate to `tally` instead of using the `go-common/metrics` wrapper?

+1 I spent 2 hours on this today ..

I have a use-case in mind for this - testing the different parts of a timeseries database with concurrent operations (user operations - reads/writes; housekeeping tasks - serialisation to disk/cleanup/etc)....

@untoldwind I'd love to get your feedback before I start implementing any of this.