Closed continuum-aditya-pingale closed 5 years ago
Affects: \.
I am trying to setup sonar widget. This is my sonar.properties file
dbname=dashboarddb dbusername=dashboarduser dbpassword=dbpassword dbhost=localhost dbport=27017 dbreplicaset=false dbhostport=localhost:27017,127.0.0.1:27017 sonar.cron=0 0/5 sonar.servers[0]=*** sonar.versions[0]=7.8 sonar.metrics[0]=ncloc,violations,new_vulnerabilities,critical_violations,major_violations,blocker_violations,tests,test_success_density,test_errors,test_failures,coverage,line_coverage,sqale_index,alert_status,quality_gate_details,new_violations,new_critical_violations,new_major_violations,new_blocker_violations,duplicated_lines,open_issues,code_smells,new_code_smells,bugs,new_bugs,new_coverage sonar.username=** sonar.password=*
here is a snippet from my log
2019-09-12 20:02:31,748 [main] ERROR o.s.boot.SpringApplication - Application startup failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'metadataRepository': Invocation of init method failed; nested exception is org.springframework.dao.DataIntegrityViolationException: Cannot create index for '' in collection 'metadata' with keys '{ "key" : 1 , "type" : 1}' and options '{ "name" : "unique_mdata_key_type" , "unique" : true}'. Index already defined as '{ "v" : 2 , "key" : { "key" : 1 , "type" : 1} , "name" : "unique_mdata_key_type" , "ns" : "dashboarddb.metadata"}'.; nested exception is com.mongodb.MongoCommandException: Command failed with error 85: 'Index with name: unique_mdata_key_type already exists with different options' on server localhost:27017. The full response is { "ok" : 0.0, "errmsg" : "Index with name: unique_mdata_key_type already exists with different options", "code" : 85, "codeName" : "IndexOptionsConflict" }
if i delete "metadeta" collection and run it, I still get errors.
@continuum-aditya-pingale this issue was fixed today, can you get the latest code from master branch and retry?
@rvema works now. Thank you
Affects: \.
I am trying to setup sonar widget. This is my sonar.properties file
dbname=dashboarddb dbusername=dashboarduser dbpassword=dbpassword dbhost=localhost dbport=27017 dbreplicaset=false dbhostport=localhost:27017,127.0.0.1:27017 sonar.cron=0 0/5 sonar.servers[0]=*** sonar.versions[0]=7.8 sonar.metrics[0]=ncloc,violations,new_vulnerabilities,critical_violations,major_violations,blocker_violations,tests,test_success_density,test_errors,test_failures,coverage,line_coverage,sqale_index,alert_status,quality_gate_details,new_violations,new_critical_violations,new_major_violations,new_blocker_violations,duplicated_lines,open_issues,code_smells,new_code_smells,bugs,new_bugs,new_coverage sonar.username=** sonar.password=*
here is a snippet from my log
2019-09-12 20:02:31,748 [main] ERROR o.s.boot.SpringApplication - Application startup failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'metadataRepository': Invocation of init method failed; nested exception is org.springframework.dao.DataIntegrityViolationException: Cannot create index for '' in collection 'metadata' with keys '{ "key" : 1 , "type" : 1}' and options '{ "name" : "unique_mdata_key_type" , "unique" : true}'. Index already defined as '{ "v" : 2 , "key" : { "key" : 1 , "type" : 1} , "name" : "unique_mdata_key_type" , "ns" : "dashboarddb.metadata"}'.; nested exception is com.mongodb.MongoCommandException: Command failed with error 85: 'Index with name: unique_mdata_key_type already exists with different options' on server localhost:27017. The full response is { "ok" : 0.0, "errmsg" : "Index with name: unique_mdata_key_type already exists with different options", "code" : 85, "codeName" : "IndexOptionsConflict" }
if i delete "metadeta" collection and run it, I still get errors.