dlmarion commented on code in PR #4208:
URL: https://github.com/apache/accumulo/pull/4208#discussion_r1476757315
##########
server/manager/src/main/java/org/apache/accumulo/manager/tableOps/tableImport/PopulateMetadataTable.java:
##########
@@ -155,11 +166,7 @@ public Repo<Manager> call(long tid, Manager manager)
throws Exception {
if (m == null || !currentRow.equals(metadataRow)) {
if (m != null) {
- if (!sawTabletAvailability) {
- // add a default tablet availability
- TabletColumnFamily.AVAILABILITY_COLUMN.put(m,
-
TabletAvailabilityUtil.toValue(TabletAvailability.ONDEMAND));
- }
+ AVAILABILITY_COLUMN.put(m,
TabletAvailabilityUtil.toValue(initialAvailability));
Review Comment:
> I think the distinction will come down to how availability is perceived.
It's defined as Tablet Availability.
> With that type of usage, the availability is not tied to the table /
data, but instead relates directly to the system usage at that point in time.
It's a tablet level setting. A tablet with an ONDEMAND tablet availability
may be hosted, or not, depending on the usage at that point in time. But it's
availability setting is ONDEMAND.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
