>But why would anyone have different configurations for streaming into the >same cache on the same node? In this case, we should print out a warning if >the configuration of one streamer is different from another. Agree?
Well, I have not come across the necessity to use different datastreamers on one node in use cases I've seen. But at the same time, I can come up with the use case in order to configure different StreamReceivers when uploading data from different data sources. Evgenii 2017-09-03 20:18 GMT+03:00 Dmitriy Setrakyan <[email protected]>: > On Sun, Sep 3, 2017 at 10:09 AM, Evgenii Zhuravlev < > [email protected] > > wrote: > > > Dmitriy, > > > > >Disagree. This is an Ignite issue, not a user issue. We must detect this > > >and either provide a user with a warning message or disallow 2 streamers > > >with identical names. > > >Makes sense? > > > > It's not a streamer name we apply as an argument, it's a cache name. So, > > it's possible to use a different Data Streamers from different nodes for > > the one cache or even different streamers for one cache on the one node. > > > > But why would anyone have different configurations for streaming into the > same cache on the same node? In this case, we should print out a warning if > the configuration of one streamer is different from another. Agree? > > > > > > Evgenii > > > > > > 2017-09-03 19:59 GMT+03:00 Dmitriy Setrakyan <[email protected]>: > > > > > On Sun, Sep 3, 2017 at 9:36 AM, Evgenii Zhuravlev < > > > [email protected]> > > > wrote: > > > > > > > What about this SO question - I think it could be a good idea to add > > some > > > > additional validation between nodes configurations at node's start. > > > > Because, if the root of the problem was found correctly, then it > means > > > that > > > > nodes were started with inconsistent configurations. What do you > think? > > > > > > > > > > Agree. These are exactly the fixes we should start adding to Ignite. > > > > > > > > > > https://stackoverflow.com/questions/45911616/ > > datastreamer-does-not-work- > > > > well/4597234 > > > > - it doesn't relate to DataStreamer, looks like since version 2.1(or > > > > earlier) we have problems with old versions of Java7. I've seen also > at > > > > least two same questions on the user list. I've created issue for > that: > > > > https://issues.apache.org/jira/browse/IGNITE-6248 > > > > > > > > > Great! I have scheduled this ticket for 2.2. The node must not start on > > an > > > incompatible Java version. > > > > > > > > > > > > > > https://stackoverflow.com/questions/45034975/apache- > > > > ignite-data-streamer/45035436 > > > > - As he said at the end, I think he didn't properly understand how > > > > DataStreamer should work > > > > > > > > > > Disagree. This is an Ignite issue, not a user issue. We must detect > this > > > and either provide a user with a warning message or disallow 2 > streamers > > > with identical names. > > > > > > Makes sense? > > > > > > > > > > > > > > http://apache-ignite-users.70518.x6.nabble.com/Failing- > > > > DataStreamer-beacuse-of-minor-version-change-td12142.html > > > > for this issue, we already have an improvement too: > > > > https://issues.apache.org/jira/browse/IGNITE-5195 > > > > > > > > > Argh, what a horrible issue. We spit out an exception 2 pages long, and > > > then telling the poor user to ignore it. This is just sad. I updated > the > > > ticket and added a link to the user thread. > > > > > > > > > > > > > > > > > > Evgenii > > > > > > > > 2017-09-03 18:13 GMT+03:00 Dmitriy Setrakyan <[email protected] > >: > > > > > > > > > In that case we either provide bad configuration or bad error > > messages. > > > > > Could we provide a better error message for this SO issue? > > > > > > > > > > Evgenii, can I please ask you to provide links to all the data > > streamer > > > > > questions you looked at here? This way we may have a chance to spot > > > some > > > > > area for improvement. > > > > > > > > > > D. > > > > > > > > > > On Sun, Sep 3, 2017 at 3:05 AM, Evgenii Zhuravlev < > > > > > [email protected]> > > > > > wrote: > > > > > > > > > > > Dmitriy, > > > > > > > > > > > > I've seen several questions on StackOverflow and on the user > list, > > > that > > > > > > seems to be connected with Data Streamer at first sight, but > after > > > some > > > > > > investigation, it was clear that they were not related to Data > > > Streamer > > > > > at > > > > > > all. Usually, as it was in this question on SO, it was a wrong > > > > > > configuration or conflicted configuration between nodes. > > > > > > > > > > > > Evgenii > > > > > > > > > > > > 2017-09-03 2:10 GMT+03:00 Dmitriy Setrakyan < > [email protected] > > >: > > > > > > > > > > > > > Igniters, > > > > > > > > > > > > > > I am noticing quite a few issues on the user list and Stack > > > Overflow > > > > > that > > > > > > > have to do with Data Streamer usability. Here is just one > > example: > > > > > > > > > > > > > > https://stackoverflow.com/questions/46015833/ > > > > > > datastreamer-adddata-method- > > > > > > > not-work-as-expected-in-cluster > > > > > > > > > > > > > > I think, as a community, we should try to analyze all the > issues > > > and > > > > > > figure > > > > > > > out why the users are struggling. > > > > > > > > > > > > > > Does anyone have a good sense for what is happening? > > > > > > > > > > > > > > D. > > > > > > > > > > > > > > > > > > > > > > > > > > > >
