The stack trace is prety heavy. Maybe I need to use channel ? At first I just want to do something that's working ,that's why I didn't use channel, goroutine etc... but if I need to...
I see you're not handling errors in your walk function callback. The stack trace indicates 'info' being nil. With os.FileInfo being an interface, it might be nil if an error occured while walking your tree.
For some debugging you can try to insert logp.Debug("filesize", "path=%v, info=%v, err=%v\n", path, info, err) and run your beat with -d "filesize".
thanks, I rewrote the method this morning. I'm currently cleaning the fmt.Printf debug message, i'm doing to commit very soon. Thanks anyway. I have to admit that this is my first "real" go code, and the stack trace scared me a bit
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.