[jira] [Commented] (DRILL-3301) ILIKE does not support escape characters.
[ https://issues.apache.org/jira/browse/DRILL-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588037#comment-14588037 ] Patrick Toole commented on DRILL-3301: -- See DRILL-2658 for a syntax description in the comments. ILIKE does not support escape characters. - Key: DRILL-3301 URL: https://issues.apache.org/jira/browse/DRILL-3301 Project: Apache Drill Issue Type: Bug Reporter: Patrick Toole The like operator properly supports escaping characters. Because the ILIKE is implemented as a function, it does not support escaping. The grammar needs to be updated to accept ILIKE in the same locations as LIKE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DRILL-3301) ILIKE does not support escape characters.
Patrick Toole created DRILL-3301: Summary: ILIKE does not support escape characters. Key: DRILL-3301 URL: https://issues.apache.org/jira/browse/DRILL-3301 Project: Apache Drill Issue Type: Bug Reporter: Patrick Toole The like operator properly supports escaping characters. Because the ILIKE is implemented as a function, it does not support escaping. The grammar needs to be updated to accept ILIKE in the same locations as LIKE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DRILL-2658) Add ilike and regex substring functions
[
https://issues.apache.org/jira/browse/DRILL-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567881#comment-14567881
]
Patrick Toole commented on DRILL-2658:
--
It appears the alias version of substr does not work (substring):
0: jdbc:drill: select substr('a','b') from sys.version;
+-+
| EXPR$0 |
+-+
| null|
+-+
1 row selected (0.288 seconds)
0: jdbc:drill: select substring('a','b') from sys.version;
Error: PARSE ERROR: From line 1, column 8 to line 1, column 25: Cannot apply
'SUBSTRING' to arguments of type 'SUBSTRING(CHAR(1) FROM CHAR(1))'.
Supported form(s): 'SUBSTRING(CHAR FROM INTEGER)'
'SUBSTRING(CHAR FROM INTEGER FOR INTEGER)'
'SUBSTRING(VARCHAR FROM INTEGER)'
'SUBSTRING(VARCHAR FROM INTEGER FOR INTEGER)'
'SUBSTRING(BINARY FROM INTEGER)'
'SUBSTRING(BINARY FROM INTEGER FOR INTEGER)'
'SUBSTRING(VARBINARY FROM INTEGER)'
'SUBSTRING(VARBINARY FROM INTEGER FOR INTEGER)'
Add ilike and regex substring functions
---
Key: DRILL-2658
URL: https://issues.apache.org/jira/browse/DRILL-2658
Project: Apache Drill
Issue Type: New Feature
Components: Functions - Drill
Reporter: Steven Phillips
Assignee: Steven Phillips
Fix For: 1.0.0
Attachments: DRILL-2658.patch, DRILL-2658.patch
This will not modify the parser, so postgress syntax such as:
... where c ILIKE '%ABC%'
will not be currently supported. It will simply be a function:
... where ILIKE(c, '%ABC%')
Same for substring:
select substr(c, 'abc')...
will be equivalent to postgress
select substr(c from 'abc'),
but 'abc' will be treated as a java regex pattern.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DRILL-2658) Add ilike and regex substring functions
[ https://issues.apache.org/jira/browse/DRILL-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567866#comment-14567866 ] Patrick Toole commented on DRILL-2658: -- This form breaks other downstream items: SELECT * FROM table_name WHERE column_name ilike '4\t' ESCAPE '\' Add ilike and regex substring functions --- Key: DRILL-2658 URL: https://issues.apache.org/jira/browse/DRILL-2658 Project: Apache Drill Issue Type: New Feature Components: Functions - Drill Reporter: Steven Phillips Assignee: Steven Phillips Fix For: 1.0.0 Attachments: DRILL-2658.patch, DRILL-2658.patch This will not modify the parser, so postgress syntax such as: ... where c ILIKE '%ABC%' will not be currently supported. It will simply be a function: ... where ILIKE(c, '%ABC%') Same for substring: select substr(c, 'abc')... will be equivalent to postgress select substr(c from 'abc'), but 'abc' will be treated as a java regex pattern. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DRILL-2614) SHOW SCHEMAS should be SHOW SCHEMATA
[ https://issues.apache.org/jira/browse/DRILL-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14391101#comment-14391101 ] Patrick Toole commented on DRILL-2614: -- It is my understanding that ANSI SQL does not get involved in Meta Data management. However, INFORMATION_SCHEMA uses SCHEMATA. Most databases have a naming convention different; ie SCHEMA / DATABASE / INSTANCE is ambiguous and different between vendors. SHOW SCHEMAS should be SHOW SCHEMATA Key: DRILL-2614 URL: https://issues.apache.org/jira/browse/DRILL-2614 Project: Apache Drill Issue Type: Improvement Components: Metadata Affects Versions: 0.7.0 Reporter: Patrick Toole Assignee: Steven Phillips Priority: Minor Fix For: 1.0.0 The plural of schema is schemata. At a minimum, both should work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DRILL-2615) 'DESC' should be short for 'DESCRIBE'
Patrick Toole created DRILL-2615: Summary: 'DESC' should be short for 'DESCRIBE' Key: DRILL-2615 URL: https://issues.apache.org/jira/browse/DRILL-2615 Project: Apache Drill Issue Type: Bug Reporter: Patrick Toole Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
