Keith Turner

> For table and namespace IDs, this would somewhat conflict with the goal to keep toString() equivalent to canonical() in the API contract for AbstractId. I was not really sure...

> The problem with using something other than toString(), is that we have to remember to explicitly convert it ourselves, and we frequently forget to do that. A log builder...

> I don't think it is a big of deal anymore to have the toString() method return a formatted string. I think most places it is used is in string...

So far it seems like there are three viable options (with the log4j specific option not being viable) - Modify toString() on AbstractId to format the id and include a...

> People will make mistakes, and not realize... whether it's concatenating a path in ZK, constructing a metadata entry That is a really good con. I edited my earlier comment...

> However, ultimately, I don't think it's necessary to bother with trying to format the toString for table IDs and namespace IDs. Most of the time when we want to...

I'll take a look at it

I think I have found one possible cause to this. Before doing the consistency check on close the following code will wait for there the be zero non-external compactions by...

Thinking about this I had a few random thoughts that I corralled into sections below. ## User experience Thinking about one possible user experience is that we have a single...

Thinking a bit more about making tablets sticky, was thinking an algorithm like the following may be sticky and resilient to high scan load on a few tablets. The algorithm...