The Product Idea boards have gotten an update to better integrate them within our Product team's idea cycle! However this update does have a few unique behaviors, if you have any questions about them check out our FAQ.

Alteryx Designer Desktop Ideas

Share your Designer Desktop product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Add Parquet data format as input & output

Please add Parquet data format ( as read-write option for Alteryx.


Apache Parquet is a columnar storage format available to any project in the Hadoop ecosystem, regardless of the choice of data processing framework, data model or programming language.


Thank you.




Alteryx Alumni (Retired)



I posted version2 of the solution in the KB.


It uses the Post Create SQL Statement to alter the table to parquet format  "ALTER TABLE table_name SET FILEFORMAT PARQUET;"


Try that.

Alteryx Alumni (Retired)
5 - Atom

I tried to access the information DurgaS shared above, but failed.  


Will product team review this and see if we can make this part of Alteryx Roadmap?  Cheers!

5 - Atom

Please add Alteryx ability to read .parquet files from apache spark. 

13 - Pulsar


Just to say that Qlik Sense is now able to read and write parquet file while Alteryx is still unable to do it.

Frankly, that's a shame since parquet has became a standard widely used these last years.

Alteryx Alumni (Retired)
Status changed to: Accepted

We are looking into adding support for Parquet in 24.1

13 - Pulsar

Hello @harsh_alang great news, thanks

17 - Castor
17 - Castor

That is an important and valuable addition!

7 - Meteor


This feature would be very much appreciated.


Using the Python tool for export is at this point unwieldy as you have to have the file loaded in Alteryx then load again in the Python tool, which is very memory intensive

5 - Atom

This is a valuable addition but why was support for this format not added to the S3 connector tools?  Parquet is a common format on S3.  S3 connectors seem neglected overall and are missing more than one QoL feature that the input/output tools have.  (Dynamic file name by appending a field, parquet, etc.).  Support for these features for AWS users with data in S3 would be appreciated.