virajjasani commented on code in PR #2225:
URL: https://github.com/apache/phoenix/pull/2225#discussion_r2208446338
##########
phoenix-core-client/src/main/java/org/apache/phoenix/query/QueryServices.java:
##########
@@ -383,6 +383,8 @@ public interface QueryServices extends SQLCloseable {
public static final String WAL_EDIT_CODEC_ATTRIB =
"hbase.regionserver.wal.codec";
//Property to know whether TTL at View Level is enabled
public static final String PHOENIX_VIEW_TTL_ENABLED =
"phoenix.view.ttl.enabled";
+ // TTL strict mode - when false, TTL is considered relaxed
+ public static final String PHOENIX_TTL_STRICT = "phoenix.ttl.strict";
Review Comment:
Yes storing it as syscat/PTable property is not bad idea, but it can be done
outside of this Jira. To keep it simpler, i believe we should scope this as
server side change i.e. configure at cluster level or table level and allow
customers to use it using CREATE TABLE or ALTER TABLE DDLs.
I can create follow-up jira to store this attribute at syscat level.
--
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: issues-unsubscr...@phoenix.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
