@Felix Albani Thanks for quick response I need to delete around 100 records , Each one having unique identity number is their any way to delete in a single shot Since below process is taking more time for million of records curl 'http://localhost:8080/solr/<core-name>/update'-H "Content-type: text/xml"--data-binary '<delete><query> dataid : 101</query></delete>' curl 'http://localhost:8080/solr/<core-name>/update'-H "Content-type: text/xml"--data-binary '<delete><query> dataid : 1058262 </query></delete>' curl 'http://localhost:8080/solr/<core-name>/update'-H "Content-type: text/xml"--data-binary '<delete><query> dataid : 74965103</query></delete>' curl 'http://localhost:8080/solr/<core-name>/update'-H "Content-type: text/xml"--data-binary '<delete><query> dataid : 1895604 </query></delete>' curl 'http://localhost:8080/solr/<core-name>/update'-H "Content-type: text/xml"--data-binary '<delete><query> dataid : 1023135</query></delete>' .... .... .... .... curl 'http://localhost:8080/solr/<core-name>/update'-H "Content-type: text/xml"--data-binary '<delete><query> dataid : 18465498</query></delete>' curl 'http://localhost:8080/solr/<core-name>/update'-H "Content-type: text/xml"--data-binary '<delete><query> dataid : 1878999</query></delete>' curl 'http://localhost:8080/solr/<core-name>/update'-H "Content-type: text/xml"--data-binary '<delete><query> dataid : 222100</query></delete>' ... View more

@Satya Nittala As the data is not in the consistent format i have 2 step method to populate field values correctly. Step1: Create an temporary table to store this intermediate step data Split the data on = character and populate the data hive> select split('hdfs://Test/lob/ebia/publish/gss_attribute_details_pub/load_dt=20170303',"=")[0] Location,split('hdfs://Test/lob/ebia/publish/gss_attribute_details_pub/load_dt=20170303',"=")[1] partitionfields; +-----------------------------------------------------------------+------------------+--+ | location | partitionfields | +-----------------------------------------------------------------+------------------+--+ | hdfs://Test/lob/ebia/publish/gss_attribute_details_pub/load_dt | 20170303 | +-----------------------------------------------------------------+------------------+--+ We are still missing load_dt in partitionfields column data Step2: select from temporary table data and insert into final table hive> select regexp_extract("hdfs://Test/lob/ebia/publish/gss_attribute_details_pub/load_dt","(.*)\\/",1) location,concat_ws("=",reverse(split(reverse('hdfs://Test/lob/ebia/publish/gss_attribute_details_pub/load_dt'), '/')[0]),"partitionfields") partitionfields; +---------------------------------------------------------+--------------------------+--+ | location | partitionfields | +---------------------------------------------------------+--------------------------+--+ | hdfs://Test/lob/ebia/publish/gss_attribute_details_pub | load_dt=partitionfields | +---------------------------------------------------------+--------------------------+--+ In step2 first i'm extracting only data before last / i.e after / the data needs to go to partitionfields column, and by using concat_ws i'm joining partitionfields column data and using reverse function with split on / then extracting [0] position value, concatenating with partitionfields value. (or) By using two regular expression extracts to prepare the actual final data for the columns hive> select regexp_extract("hdfs://Test/lob/ebia/publish/gss_attribute_details_pub/load_dt","(.*)\\/",1) location,concat_ws("=",regexp_extract('hdfs://Test/lob/ebia/publish/gss_attribute_details_pub/load_dt', '(.*)\/(.*)',2),"partitionfields") partitionfields; +---------------------------------------------------------+--------------------------+--+ | location | partitionfields | +---------------------------------------------------------+--------------------------+--+ | hdfs://Test/lob/ebia/publish/gss_attribute_details_pub | load_dt=partitionfields | +---------------------------------------------------------+--------------------------+--+ I hope this will work for your case correctly. ... View more

Please take a look at these models that we recently added. ... View more

@Shu , Thank You...its working.. ... View more

@Ashutosh Mestry , Its Syntax Mistake, Now working Fine..Thanks....!!! ... View more

@Laura Ngo , I tried with POST also , Same issue, Its not reflecting ... View more

@Satya Nittala 1. Please use correct port . By default , Atlas in non-SSL environment is configured to use 21000. 2. curl requires "@" for providing files. Example : -d @user/testplace.json 3. To update type , "PUT" (not POST. To create types use POST, to update types use "PUT") the JSON to http://atlashost:21000/api/atlas/v2/types/typedefs 4. As already mentioned , classification/tag best suits your requirement. Its highly recommended to use tags instead of updating types. ... View more

Thank You @Sharmadha Sainath , It is working Fine 🙂 ... View more