Hi,
CSV schemas formats are based on delimited schemas which are meant to be
sequence sensitive ref : DelimitedSchema
<https://github.com/apache/apex-malhar/blob/master/contrib/src/main/java/com/datatorrent/contrib/parser/DelimitedSchema.java>
and
don't have a notion of input to output field mappings.
Field info mappings for output operators are typically are a of the form -
destFieldName:pojoFieldName:type/supportType and are not intended to be
sequence sensitive.
We can go with a JSON based structure which maps sources to destinations
with their respective types,
{
"destinationFieldName": "destination field name",
"destType" : "support type, type",
"srcFieldName" : "source pojo field name",
"srcType" : "support type, type",
"constraints" : "constraint expression"
}
Thanks,
Dev
Thanks,
Dev
On Mon, Nov 14, 2016 at 9:27 AM, Ashwin Chandra Putta <
[email protected]> wrote:
> Hitesh,
>
> We should standardize the schema definition across apex for individual
> operators and tuple classes.
>
> I think you should be able to use schema definition for CSV parser without
> the delimiter.
>
> Regards,
> Ashwin.
>
> On Nov 14, 2016 2:45 AM, "Hitesh Kapoor" <[email protected]> wrote:
>
> > Hi All,
> >
> > Currently in JdbcPOJOInsertOuput operator we cannot configure
> JdbcFieldInfo
> > via properties.xml and the user has to do the necessary coding in his
> > application.
> >
> > To implement this improvement, the approach mentioned in
> > http://docs.datatorrent.com/application_packages/#operator-properties
> > could
> > be followed.
> > Now we need to provide the user a format for specifying the value of
> > fieldInfo.
> >
> > Kindly let me know which of the following is the best format to be used
> for
> > this
> > 1) CSV string (or any delimited string) with values for data members of
> > JdbcFieldInfo in a fixed sequence.
> > 2) JSON format with appropriate mapping.
> > 3) XML format with appropriate name tags and values.
> >
> > Regards,
> > Hitesh
> >
>
