alanblueshift commented on issue #1018: Scan command now can produce results as 
csv and json. Related to #984
   @keith-turner what do you think with we have a kind of interface on API 
module? Something like this:
   In that way, we could work in different scan formats without worrying about 
changes the org.apache.fluo.command.FluoScan class every time.
   For example: If someone wish to implement an avro exporter for the scan, 
what will it be the parameters?
   Imagine we could call the scan command like this:
   > fluo scan -a myapp --type avro \
   --parameter "avro.schema.url=hdfs://user/xxx/schemas/file.avsc" \
   --parameter "avro.output.codec=snappy"
   The Apache Camel project uses a file with the name of component to 
instantiate the right factory class of the component. For example, when an user 
invoke "hbase:mytable..." to insert something on HBase , there is a file called 
**hbase** on the META-INF folder that points to right component on classpath.
   We could use that strategy to implement different formats on scan without 
insert dependencies on fluo project directly.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to