ASF GitHub Bot commented on NIFI-2613:

Github user jvwing commented on the issue:

    @jdye64 I still had trouble building and running NiFi with this PR.
    * root POM still references nifi-poi-bundle version "1.0-SNAPSHOT"
    * nifi-poi-nar still has a dependency on nifi-poi-processors version 
    * NiFi fails to start processing the entry for 
org.apache.nifi.processors.kite.ConvertAvroToParquet in 
 (unintentionally included in commit?)
    Would you please try running `mvn clean install -Pcontrib-check`, verifying 
that the latest nifi-poi-nar is included in the lib output, and that NiFi 
starts OK?

> Support extracting content from Microsoft Excel (.xlxs) documents
> -----------------------------------------------------------------
>                 Key: NIFI-2613
>                 URL: https://issues.apache.org/jira/browse/NIFI-2613
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Jeremy Dyer
>            Assignee: Jeremy Dyer
> Microsoft Excel is a wildly popular application that businesses rely heavily 
> on to store, visualize, and calculate data. Any single company most likely 
> has thousands of Excel documents containing data that could be very valuable 
> if ingested via NiFi and combined with other datasources. Apache POI is a 
> popular 100% Java library for parsing several Microsoft document formats 
> including Excel. Apache POI is extremely flexible and can do several things. 
> This issue would focus solely on using Apache POI to parse an incoming .xlxs 
> document and convert it to CSV. The processor should be capable of limiting 
> which excel sheets. CSV seems like the natural choice for outputting each row 
> since this feature is already available in Excel and feels very natural to 
> most Excel sheet designs.
> This capability should most likely introduce a new "poi" module as I envision 
> many more capabilities around parsing Microsoft documents could come from 
> this base effort.

This message was sent by Atlassian JIRA

Reply via email to