Github user babokim commented on a diff in the pull request:
https://github.com/apache/tajo/pull/232#discussion_r20338252
--- Diff: tajo-common/src/main/java/org/apache/tajo/conf/TajoConf.java ---
@@ -302,6 +302,8 @@ public static int setDateOrder(int dateOrder) {
HISTORY_EXPIRY_TIME_DAY("tajo.history.expiry-time-day", 7),
// Misc
-------------------------------------------------------------------
+ // Fragment
+
FRAGMENT_ALTERNATIVE_UNKNOWN_LENGTH("tajo.fragment.alternative.unknown.length",
(long)(512 * 1024 * 1024)),
--- End diff --
When making physical plan, the length of fragment is used to determine the
physical operation.
But some storage does not know the size of the fragment. In this case
PhysicalPlanner uses this value to determine.
I will add comments.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
