Github user hyunsik commented on a diff in the pull request:
https://github.com/apache/tajo/pull/138#discussion_r17601535
--- Diff: tajo-common/src/main/java/org/apache/tajo/conf/TajoConf.java ---
@@ -353,7 +353,10 @@ public static int setDateOrder(int dateOrder) {
$TEST_MIN_TASK_NUM("tajo.test.min-task-num", -1),
// Behavior Control
---------------------------------------------------------
- $BEHAVIOR_ARITHMETIC_ABORT("tajo.behavior.arithmetic-abort", false);
+ $BEHAVIOR_ARITHMETIC_ABORT("tajo.behavior.arithmetic-abort", false),
+
+ // ResultSet ---------------------------------------------------------
+ $RESULT_SET_FETCH_SIZE("tajo.resultset.fetch.size", 200)
--- End diff --
It may be the number of rows. I have a suggestion. In my view,
```fetch.row-num``` is more intuitive. ```fetch.size``` is relatively
mis-understandable, and it seems to be the number of bytes rather than the
number of rows. It's because we have used ```size``` prefix for the number of
bytes in many config keys.
---
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.
---
