[
https://issues.apache.org/jira/browse/HAWQ-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366856#comment-15366856
]
ASF GitHub Bot commented on HAWQ-779:
-------------------------------------
Github user shivzone commented on a diff in the pull request:
https://github.com/apache/incubator-hawq/pull/779#discussion_r69996058
--- Diff: src/backend/access/external/test/pxffilters_test.c ---
@@ -61,7 +62,7 @@ test__supported_filter_type(void **state)
/* go over pxf_supported_types array */
int nargs = sizeof(pxf_supported_types) / sizeof(Oid);
- assert_int_equal(nargs, 12);
+ assert_int_equal(nargs, 13);
--- End diff --
Updated to derive size based on expected array size
> support more pxf filter pushdwon
> ---------------------------------
>
> Key: HAWQ-779
> URL: https://issues.apache.org/jira/browse/HAWQ-779
> Project: Apache HAWQ
> Issue Type: New Feature
> Components: PXF
> Reporter: Devin Jia
> Assignee: Shivram Mani
> Fix For: 2.0.0
>
>
> When I use the pxf hawq, I need to read a traditional relational database
> systems and solr by way of the external table. The project
> :https://github.com/Pivotal-Field-Engineering/pxf-field/tree/master/jdbc-pxf-ext,
> only "WriteAccessor ",so I developed 2 plug-ins, the projects:
> https://github.com/inspur-insight/pxf-plugin , But these two plug-ins need to
> modified HAWQ:
> 1. When get a list of fragment from pxf services, push down the
> 'filterString'. modify the backend / optimizer / plan / createplan.c of
> create_pxf_plan methods:
> segdb_work_map = map_hddata_2gp_segments (uri_str,
> total_segs, segs_participating,
> relation, ctx-> root-> parse-> jointree-> quals);
> 2. modify pxffilters.h and pxffilters.c, support TEXT types LIKE operation,
> Date type data operator, Float type operator.
> 3. Modify org.apache.hawq.pxf.api.FilterParser.java, support the LIKE
> operator.
> I already created a feature branch in my local ,and tested.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
