That is not something I explicitely decided. I took the toElasticsearch AS a base and there it is set like this.

If its unnecessary it could be removed as I don't need it for my part.

Leo.

On March 18, 2014 7:30:50 PM CET, Erica Pisani <notifications@github.com> wrote:
>> +	quit      chan interface{}
>> +	url       string
>> +	name      string
>> +	entities  []string
>> +	value     string
>> +	parsedValue     *jee.TokenTree
>> +}
>> +
>> +// we need to build a simple factory so that streamtools can make
>new blocks of this kind
>> +func NewToStreamdrill() blocks.BlockInterface {
>> +	return &ToStreamdrill{}
>> +}
>> +
>> +// Setup is called once before running the block. We build up the
>channels and specify what kind of block this is.
>> +func (b *ToStreamdrill) Setup() {
>> +	b.Kind = "ToStreamdrill"
>
>I just have a small question (entirely out of curiosity): Why did you
>decide to create and assign the `Kind` attribute in the setup as
>opposed to having it as a default already built into the structure? 
>Or maybe making the `Kind` attribute something like `value` where you
>have:
>
>````
>type ToStreamdrill struct {
>	blocks.Block
>	queryrule chan chan interface{}
>	inrule    chan interface{}
>	in        chan interface{}
>	out       chan interface{}
>	quit      chan interface{}
>	url       string
>	name      string
>	entities  []string
>	value     string
>    Kind      string
> 	parsedValue     *jee.TokenTree
> }
>````
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/nytlabs/streamtools/pull/308/files#r10718533

-- 
thinkberg.com | realtime insights