Github user arina-ielchiieva commented on a diff in the pull request:
https://github.com/apache/drill/pull/819#discussion_r113908201
--- Diff: common/src/main/java/org/apache/drill/common/types/Types.java ---
@@ -636,43 +658,63 @@ public static String toString(final MajorType type) {
/**
* Get the <code>precision</code> of given type.
- * @param majorType
- * @return
+ *
+ * @param majorType major type
+ * @return precision value
*/
public static int getPrecision(MajorType majorType) {
- MinorType type = majorType.getMinorType();
-
- if (type == MinorType.VARBINARY || type == MinorType.VARCHAR) {
- return 65536;
- }
-
if (majorType.hasPrecision()) {
return majorType.getPrecision();
}
- return 0;
+ return isScalarStringType(majorType) ? MAX_VARCHAR_LENGTH : UNDEFINED;
--- End diff --
Currently Drill does not consider length change in varchar as schema change.
Regarding sampling data, since Drill is schema-less, I think it's OK to
return unknown or max length, sampling won't give exact result any way and will
complicate query process. This PR will help users who want to have length to be
specified (ex: by means of cast function usage).
---
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.
---
