[ 
https://issues.apache.org/jira/browse/NIFI-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515401#comment-16515401
 ] 

ASF GitHub Bot commented on NIFI-5166:
--------------------------------------

Github user ijokarumawak commented on the issue:

    https://github.com/apache/nifi/pull/2686
  
    Hi @mans2singh 
    
    Thanks for sharing the templates. I will try it later but I understand how 
it works by using RDMBS to join input data and classification results.
    
    I think we need to provide more toolset so that people can use DL4J easily 
from NiFi flows. So a couple of points for further discussion:
    
    1. Have you ever considered a DL4J component implementing RecordLookup 
interface so that LookupRecord processor? I've mentioned about this before. 
Once we provide this pattern, RDBMS is no longer required to use evaluation 
result in later flow.
    
    2. How would NiFi user convert a raw data (CSV, text, images, audio ... 
etc) into vector format that can be fed to DL4J Networks? I haven't explored 
yet myself, but can we provide some other Processors or RecordReader/Writers to 
do vectorization process, probably using DataVec? 
https://deeplearning4j.org/datavec
    
    
    I will ask dev ML to see if there's anyone to join the review process, too. 
Thanks!


> Create deep learning classification and regression processor
> ------------------------------------------------------------
>
>                 Key: NIFI-5166
>                 URL: https://issues.apache.org/jira/browse/NIFI-5166
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>    Affects Versions: 1.6.0
>            Reporter: Mans Singh
>            Assignee: Mans Singh
>            Priority: Minor
>              Labels: Learning, classification,, deep, regression,
>             Fix For: 1.7.0
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> We need a deep learning classification and regression processor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to