Sorry for any pain caused Thomas. Yeah, we've been trying to move off KeyValue with a while (KeyValue was marked audience private in 2012 -- 0.95). We've been trying to offer the Cell Interface in its stead so we can freely change the representation.
On timestamp setting too, ideally, we want to be able to change the format also (HLC for example). That said, we should be able to work out something here around timestamp setting by CPs in the meantime. Suggest you file a blocker against 3.0 that prevents the removal of these deprecated metjhods at least w/o first specifying alternatives. Throw in there how timestamps are used currently so we can together work out how to go forward. Thanks, S On Tue, Apr 2, 2019 at 9:59 AM Thomas D'Silva <[email protected]> wrote: > Pre 2.0 the cells objects are NoTagsKeyValue (which extend KeyValue). In > 2.0 they are NoTagsByteBufferKeyValue (which doesn't extend KeyValue) > so we cannot use the KeyValue.setTimestamp api. > > Thanks, > Thomas > > On Sun, Mar 31, 2019 at 2:03 PM Wellington Chevreuil < > [email protected]> wrote: > > > You could risk use PrivateCellUtil.setTimestamp() method, but it may > break > > in future releases since PrivateCellUtil is marked > > as @InterfaceAudience.Private. Another option, given both Put and Delete > > map to KeyValue cell type, is to check if the Cell type is KeyValue, then > > do a cast to access setTimestamp method on the KV. > > > > Em sex, 29 de mar de 2019 às 22:34, Thomas D'Silva > > <[email protected]> escreveu: > > > > > In HBase 2.0 since CellUtil.setTimestamp has been deprecated, what is > the > > > correct way to set the timestamp of a cell from a coprocessor? Phoenix > > uses > > > this API to set the timestamp of a call in our mutable indexing > > coprocessor > > > (see https://issues.apache.org/jira/browse/PHOENIX-5219). > > > > > > Thanks, > > > Thomas > > > > > >
