Hi, If the user wants to find out which file the event came from (if there is a use case as such), then he can create separate sources for each file.
Some problems with above approach would be: - if the user does not know the file names before hand, above is not a solution - when there are many files, user will have to create many streams Another option I can think of is introducing a transport property to contain the file name; something like *trp:file-name.* IMO, introducing a transport property would be better if we really have this use case that user wants to know which the event came from. Thank you, Dilini On Thu, Jun 29, 2017 at 11:44 AM, Minudika Malshan <[email protected]> wrote: > Hi all, > > In proposed Sindhi-io-file : source, the user will be providing a uri of > a directory mentioning that tailing enabled or not. > If tailing is enabled, all the files will be consumed and the connection > will be kept alive in order to check whether a new record added to the file > later. > > In this case, files in the directory will have to be consumed in parallel > and events will be created for each added record accordingly. Issue is, > will it be OK to create events without a way for the user to know what file > is related to that event? > > Thanks and regards! > -- > *Minudika Gammanpila* > Software Engineer - WSO2 > > Email : [email protected] > Mobile : +94715659887 <+94%2071%20565%209887> > Web : http://wso2.com <http://wso2.com/signature> > -- *Dilini Muthumala* Senior Software Engineer, WSO2 Inc. *E-mail :* [email protected] *Mobile: *+94 713-400-029
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
