Anyways, thanks for your reply.
On Thu, Apr 28, 2016 at 1:59 PM, Hannu Kröger <hkro...@gmail.com> wrote: > Ok, then I don’t understand the problem. > > Hannu > > On 28 Apr 2016, at 11:19, Siddharth Verma <verma.siddha...@snapdeal.com> > wrote: > > Hi Hannu, > > Had the issue been caused due to read, the insert, and delete statement > would have been erroneous. > "I saw the stdout from web-ui of spark, and the query along with true was > printed for both the queries.". > The statements were correct as seen on the UI. > Thanks, > Siddharth Verma > > > > On Thu, Apr 28, 2016 at 1:22 PM, Hannu Kröger <hkro...@gmail.com> wrote: > >> Hi, >> >> could it be consistency level issue? If you use ONE for reads and writes, >> might be that sometimes you don't get what you are writing. >> >> See: >> >> https://docs.datastax.com/en/cassandra/2.0/cassandra/dml/dml_config_consistency_c.html >> >> Br, >> Hannu >> >> >> 2016-04-27 20:41 GMT+03:00 Siddharth Verma <verma.siddha...@snapdeal.com> >> : >> >>> Hi, >>> I dont know, if someone has faced this problem or not. >>> I am running a job where some data is loaded from cassandra table. From >>> that data, i make some insert and delete statements. >>> and execute it (using forEach) >>> >>> Code snippet: >>> boolean deleteStatus= >>> connector.openSession().execute(delete).wasApplied(); >>> boolean insertStatus = >>> connector.openSession().execute(insert).wasApplied(); >>> System.out.println(delete+":"+deleteStatus); >>> System.out.println(insert+":"+insertStatus); >>> >>> When i run it locally, i see the respective results in the table. >>> >>> However when i run it on a cluster, sometimes the result is displayed >>> and sometime the changes don't take place. >>> I saw the stdout from web-ui of spark, and the query along with true was >>> printed for both the queries. >>> >>> I can't understand, what could be the issue. >>> >>> Any help would be appreciated. >>> >>> Thanks, >>> Siddharth Verma >>> >> >> > >