Problem: Use the @slf4j annotation with IDEA, then write
log.debug("debug...") );
File -- "Settings --" plugins -- "
File --" Settings -- "plugins --

Problem: Use the @slf4j annotation with IDEA, then write
log.debug("debug...") );
File -- "Settings --" plugins -- "
File --" Settings -- "plugins --




First, if the primary key is not a required field, the primary key is not used
The second way is to remove the duplicate from the table and start the operation
Thanks for watching!
1. First of all, confirm whether the Maven and Maven Repository used by IDEA are the repositories you need. If not specified, IDEA will use its own Maven and repository. The FIile – & gt; Setting – & gt; Build, the Excution, Deployment – & gt; Maven View:

2, After switching to the correct Maven and warehouse, if the error is still reported, you can delete the error JAR, and then Reimport (the circular arrow icon in the following figure), let the project to reload the JAR package.
TypeError: list indices must be integers or slices, not STR. Inquiring the information was solved
TypeError: list indices must be integers or slices, not str

: List index must be teger o>mark> slice <>ark>, not STR <>> : tas mark>9: 
0> br>1:
: <>> : :>rk> STR >>
: datas :









: : Users\WIN10\.AndroidStudio3.4
a = 4
c=a[2]
Error: line 2, in <; module>
c = a [2]
TypeError: ‘int’ object is not subscriptable
Or a more complicated one: two dimensions
a = [1,2,3,4]
c=a[2][2]
It’s a one-dimensional array, but you take an array and then you subscript it, same problem.
Caused by: java.lang.IllegalArgumentException: mapper [personName] of different type, current_type [text], merged_type [keyword]
Error creating bean with name ‘ownerOpenRecordRepository’:
If you don’t have experience with Elasticsearch, you may not know how to do it, so this article will start from scratch to solve the problem!
The first step, with our programmer’s instinct, is that the field type changes, that type changes how to do?
If in the development environment: you can access ES through the Web management terminal Kibana, you can directly delete the index that reported the error. The Internet said that it needs to be rebuilt, but in fact, it does not need to be deleted, because it is not in the production environment. It is created automatically when the project starts the instantiation. The specific operation steps are as follows;
1. First find the specific index that reported the error (the index in ES can be understood as the database), then how to find it?
The answer, of course, is to look at the log. ES will normally report an error when SpringBoot is started to connect. In the day
When we instantiate a Bean, we get an error in a Repository or something like a ×××Repository. That’s it.
2, through the address
http://118.31.60.110/###-kibana/app/kibana#/dev_tools/console?_g=()
Access the web side of ES to delete, 118.31.60.110 is the public network IP of the server where ES is located, if there is ngIx, then this IP is the IP address of ngIx, ###-kibana is also the configured item in Nginx. After successful connection, it is shown in the figure below:

Delete index
Send a RESTful style HTTP request to the Console for the delete operation, as shown below
DELETE ds##record/_search
DS# # Record is the index name. If the method is not found, write DS# # Record directly. Then click on the right side of the path similar to the playback button can be deleted successfully
4. No error was reported when starting
If you are in production, you need to export the index, then delete and rebuild it, and finally import it again. The basic pattern is the same.