html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/1614#issuecomment-398172901,https://api.github.com/repos/pydata/xarray/issues/1614,398172901,MDEyOklzc3VlQ29tbWVudDM5ODE3MjkwMQ==,5635139,2018-06-18T19:46:39Z,2020-03-26T20:39:49Z,MEMBER,"> consider some kind of history tracker as part of the metadata propagation? 

Data lineage is a big, hard, unsolved problem (~for us~ internally, above both naming things and cache invalidation :) )

To second @shoyer, I think it's big and difficult enough to be a separate library","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,264049503
https://github.com/pydata/xarray/issues/1614#issuecomment-435621629,https://api.github.com/repos/pydata/xarray/issues/1614,435621629,MDEyOklzc3VlQ29tbWVudDQzNTYyMTYyOQ==,1217238,2018-11-03T21:18:11Z,2018-11-03T21:18:11Z,MEMBER,"> I would happy to add a global keep_attrs option to xarray.set_options(), which we could use for controlling arithmetic. I'm not planning on working on it personally, but I would be happy to review a PR.

Note that this was implemented by @TomNicholas in https://github.com/pydata/xarray/pull/2482","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,264049503
https://github.com/pydata/xarray/issues/1614#issuecomment-398204944,https://api.github.com/repos/pydata/xarray/issues/1614,398204944,MDEyOklzc3VlQ29tbWVudDM5ODIwNDk0NA==,1217238,2018-06-18T21:41:46Z,2018-06-18T21:41:46Z,MEMBER,"I would happy to add a global `keep_attrs` option to `xarray.set_options()`, which we could use for controlling arithmetic. I'm not planning on working on it personally, but I would be happy to review a PR.","{""total_count"": 4, ""+1"": 4, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,264049503
https://github.com/pydata/xarray/issues/1614#issuecomment-398197376,https://api.github.com/repos/pydata/xarray/issues/1614,398197376,MDEyOklzc3VlQ29tbWVudDM5ODE5NzM3Ng==,1217238,2018-06-18T21:12:18Z,2018-06-18T21:12:18Z,MEMBER,"> No, just the proposed feature to keep or delete metadata based on the various operations. Is this behaviour already part of the library, and this issue is just to clarify the intended behaviour, or is this a feature proposal?

We already have most of this behavior (matching what @jhamman lists in the first comment), though it isn't clearly documented. It should just work if you use xarray methods/functions.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,264049503
https://github.com/pydata/xarray/issues/1614#issuecomment-398153267,https://api.github.com/repos/pydata/xarray/issues/1614,398153267,MDEyOklzc3VlQ29tbWVudDM5ODE1MzI2Nw==,1217238,2018-06-18T18:36:50Z,2018-06-18T18:36:50Z,MEMBER,"> Also - might I suggest you consider some kind of history tracker as part of the metadata propagation? 

Certainly this would be out of scope for xarray itself, but this perhaps be done with a library that wraps xarray's API. If I recall correctly, @pwolfram was also interested in this.

We did discuss customizable hooks for attribute handling in #988 but I'm no longer sure that is a good idea. These sort of overloads are really hard to get right, as we've seen with NumPy's long history of different override protocols (the most recent example being `__array_ufunc__`).","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,264049503
https://github.com/pydata/xarray/issues/1614#issuecomment-398151360,https://api.github.com/repos/pydata/xarray/issues/1614,398151360,MDEyOklzc3VlQ29tbWVudDM5ODE1MTM2MA==,1217238,2018-06-18T18:30:16Z,2018-06-18T18:30:16Z,MEMBER,"> Hi, this feature would be very relevant to the intended use case of a project I'd like to use xarray for. Is the behaviour discussed in the first post implemented anywhere, e.g. in the trunk, for me to play with?

are you referring to a different issue? the first post only summarizes some simple proposed rules.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,264049503
https://github.com/pydata/xarray/issues/1614#issuecomment-362752398,https://api.github.com/repos/pydata/xarray/issues/1614,362752398,MDEyOklzc3VlQ29tbWVudDM2Mjc1MjM5OA==,1217238,2018-02-03T00:38:12Z,2018-02-03T00:38:12Z,MEMBER,"The challenge with a user-specified function is that there can potentially be weird conflicts if multiple libraries try to override it. Possibly it's worth it for the convenience, but subclasses allowing for explicit hooks (like numpy) is probably the cleanest solution.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,264049503