pxf | Platform Extension Framework : Federated Query Engine

by greenplum-db Java Version: release-6.6.0 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | pxf Summary

pxf is a Java library typically used in Institutions, Learning, Administration, Public Services, Big Data, Amazon S3, Hadoop applications. pxf has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However pxf build file is not available. You can download it from GitHub.

PXF Build [Concourse Build Status] | PXF Certification

Support

Quality

Security

License

Reuse

Support

pxf has a low active ecosystem.

It has 67 star(s) with 53 fork(s). There are 17 watchers for this library.

It had no major release in the last 12 months.

There are 12 open issues and 58 have been closed. On average issues are closed in 149 days. There are 11 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of pxf is release-6.6.0

Quality

pxf has 0 bugs and 0 code smells.

Security

pxf has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

pxf code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

pxf is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

pxf releases are available to install and integrate.

pxf has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions are not available. Examples and code snippets are available.

pxf saves you 101855 person hours of effort in developing the same functionality from scratch.

It has 112905 lines of code, 9310 functions and 1590 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed pxf and discovered the below as its top functions. This is intended to give you an instant insight into pxf implemented functionality, and help decide if they suit your requirements.

Adds rows to the table .
Parses the request and returns a RequestContext object .
Compare the psql output for a psql output
Gets the nodes after the given node .
initialize partition fields
Fetch the metadata for a table .
Populate a single record .
Reads the next object with the given name .
Builds the filter value .
Adds a field to the given group .

Get all kandi verified functions for this library.

pxf Key Features

No Key Features are available at this moment for pxf.

pxf Examples and Code Snippets

No Code Snippets are available at this moment for pxf.

Community Discussions

Trending Discussions on pxf

ANTLR4 no viable alternative at input 'do { return' error?

Why is my ANTLR4 parser grammar erroring 'no viable alternative at input'?

Does Greenplum PXF support HDFS short circuit read?

QUESTION

ANTLR4 no viable alternative at input 'do { return' error?

Asked 2021-Mar-27 at 14:13

This ANTLR4 parser grammar errors a 'no viable alternative' error when I try to parse an input. The only rules I know of that matches the part of the input with the error are the rules 'retblock_expr' and 'block_expr'. I have put 'retblock_expr' infront of 'block_expr' and put 'non_assign_expr' infront of 'retblock_expr' but it still throws the error.

input:

print(do { return a[3] })

full error:

line 1:11 no viable alternative at input '(do { return'

parser grammar:

...

ANSWER

Answered 2021-Mar-27 at 14:13

Your PRINT token can only be matched by the blk_expr rule through this path:

There is no path for retblock_expr to recognize anything that begins with the PRINT token.

As a result, it will not matter which order you have elk_expr or retblock_expr.

There is no parser rule in your grammar that will match a PRINT token followed by a LPR token. a block_expr is matched by the program rule, and it only matches (ignoring wsp) block_expr or retblock_expr. Neither of these have alternatives that begin with an LPR token, so ANTLR can't match that token.

print(...) would normally be matched as a function call expression that accepts 0 or more comma-separated parameters. You have no sure rule/alternative defined. (I'd guess that it should be an alternative on either retblock_expr or block_expr

That's the immediate cause of this error. ANTLR really does not have any rule/alternative that can accept a LPR token in this position.

Source https://stackoverflow.com/questions/66831117

QUESTION

Why is my ANTLR4 parser grammar erroring 'no viable alternative at input'?

Asked 2021-Mar-25 at 02:52

When I run my grammar (lexer and parser) in powershell, it produces these errors:

...

ANSWER

Answered 2021-Mar-23 at 10:50

Both global and a are listed in your grammer under kwr rule.

kwr is mentioned in the inl rule which isn't used anywhere. So your parser don't know how to deal with inl and don't know what to do with two inl chained together (global a)

Source https://stackoverflow.com/questions/66761457

QUESTION

Does Greenplum PXF support HDFS short circuit read?

Asked 2020-Apr-22 at 17:07

I wonder if Greenplum PXF can take advantage of HDFS short circuit read when we place pxf and datanode on the same host. We did a prelimiary test, however, it seems that pxf does not leverage the short circuit read. There is almost nothing after googling, so we are not sure if we miss something. We use Greenplum 6.4 (community version), pxf 5.11.2 and CDH 6.3.

Any references, suggestions or comments are very appreciated.

...

ANSWER

Answered 2020-Apr-22 at 15:56

The old version of PXF with hawq actually resides with data nodes and utilizes short-circuit read. THe current PXF has changed to reside with Greenplum segment hosts and acts like a hdfs client. I think you can tweak pxf source codes and setup pxf on datanodes with short-circuit read. However, you speed up the hdfs<->pxf communication, but slow down pxf<->greenplum segment communication.

Source https://stackoverflow.com/questions/61358819

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install pxf

You can download it from GitHub.
You can use pxf like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the pxf component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: