Spring 数据弹性和递归文档映射

Spring Data Elastic and recursive document mapping

我有一个 Spring 应用程序,我在其中使用 Spring Data Elastic 来访问 Elasticsearch 数据。

数据模型需要递归,这让 Spring Data Elastic 头疼,因为我在尝试 [=34] 时得到 java.lang.WhosebugError: null =] 我的应用程序。

这是我的 class 的样子:

@Document(indexName = "conversation", type = "folder-tree")
public class MailFolderTreeSearchEntity extends DeletableEntity {

  @Id
  @Field(index = not_analyzed)
  private String id;

  @Field(type = FieldType.String, index = not_analyzed)
  private String owner;

  @Field(type = FieldType.Nested)
  private List<MailFolder> folderList;

  ...

嵌套class:

public class MailFolder {

  @Field(type = FieldType.String, index = not_analyzed)
  private String id;

  @Field(type = FieldType.String, index = not_analyzed)
  private String name;

  @Field(type = FieldType.String, index = not_analyzed)
  private String icon;

  @Field(type = FieldType.Nested)
  private List<MailFolder> children;

  ...

这是我在尝试 运行 代码时遇到的异常:

Caused by: java.lang.WhosebugError: null
at sun.reflect.generics.parser.SignatureParser.parseClassTypeSignature(SignatureParser.java:310) ~[na:1.8.0_91]
at sun.reflect.generics.parser.SignatureParser.parseFieldTypeSignature(SignatureParser.java:289) ~[na:1.8.0_91]
at sun.reflect.generics.parser.SignatureParser.parseFieldTypeSignature(SignatureParser.java:283) ~[na:1.8.0_91]
at sun.reflect.generics.parser.SignatureParser.parseTypeArgument(SignatureParser.java:436) ~[na:1.8.0_91]
at sun.reflect.generics.parser.SignatureParser.parseTypeArguments(SignatureParser.java:396) ~[na:1.8.0_91]
at sun.reflect.generics.parser.SignatureParser.parsePackageNameAndSimpleClassTypeSignature(SignatureParser.java:346) ~[na:1.8.0_91]
at sun.reflect.generics.parser.SignatureParser.parseClassTypeSignature(SignatureParser.java:310) ~[na:1.8.0_91]
at sun.reflect.generics.parser.SignatureParser.parseFieldTypeSignature(SignatureParser.java:289) ~[na:1.8.0_91]
at sun.reflect.generics.parser.SignatureParser.parseFieldTypeSignature(SignatureParser.java:283) ~[na:1.8.0_91]
at sun.reflect.generics.parser.SignatureParser.parseTypeSignature(SignatureParser.java:485) ~[na:1.8.0_91]
at sun.reflect.generics.parser.SignatureParser.parseTypeSig(SignatureParser.java:188) ~[na:1.8.0_91]
at sun.reflect.generics.repository.FieldRepository.parse(FieldRepository.java:52) ~[na:1.8.0_91]
at sun.reflect.generics.repository.FieldRepository.parse(FieldRepository.java:42) ~[na:1.8.0_91]
at sun.reflect.generics.repository.AbstractRepository.<init>(AbstractRepository.java:74) ~[na:1.8.0_91]
at sun.reflect.generics.repository.FieldRepository.<init>(FieldRepository.java:48) ~[na:1.8.0_91]
at sun.reflect.generics.repository.FieldRepository.make(FieldRepository.java:66) ~[na:1.8.0_91]
at java.lang.reflect.Field.getGenericInfo(Field.java:105) ~[na:1.8.0_91]
at java.lang.reflect.Field.getGenericType(Field.java:247) ~[na:1.8.0_91]
at org.springframework.core.SerializableTypeWrapper$FieldTypeProvider.getType(SerializableTypeWrapper.java:285) ~[spring-core-4.3.8.RELEASE.jar:4.3.8.RELEASE]
at org.springframework.core.SerializableTypeWrapper.forTypeProvider(SerializableTypeWrapper.java:150) ~[spring-core-4.3.8.RELEASE.jar:4.3.8.RELEASE]
at org.springframework.core.ResolvableType.forType(ResolvableType.java:1333) ~[spring-core-4.3.8.RELEASE.jar:4.3.8.RELEASE]
at org.springframework.core.ResolvableType.forField(ResolvableType.java:1053) ~[spring-core-4.3.8.RELEASE.jar:4.3.8.RELEASE]
at org.springframework.core.GenericCollectionTypeResolver.getCollectionFieldType(GenericCollectionTypeResolver.java:79) ~[spring-core-4.3.8.RELEASE.jar:4.3.8.RELEASE]
at org.springframework.data.elasticsearch.core.MappingBuilder.getFieldType(MappingBuilder.java:321) ~[spring-data-elasticsearch-2.1.3.RELEASE.jar:na]
at org.springframework.data.elasticsearch.core.MappingBuilder.isEntity(MappingBuilder.java:312) ~[spring-data-elasticsearch-2.1.3.RELEASE.jar:na]
at org.springframework.data.elasticsearch.core.MappingBuilder.mapEntity(MappingBuilder.java:132) ~[spring-data-elasticsearch-2.1.3.RELEASE.jar:na]
at org.springframework.data.elasticsearch.core.MappingBuilder.mapEntity(MappingBuilder.java:137) ~[spring-data-elasticsearch-2.1.3.RELEASE.jar:na]
at org.springframework.data.elasticsearch.core.MappingBuilder.mapEntity(MappingBuilder.java:137) ~[spring-data-elasticsearch-2.1.3.RELEASE.jar:na]
at org.springframework.data.elasticsearch.core.MappingBuilder.mapEntity(MappingBuilder.java:137) ~[spring-data-elasticsearch-2.1.3.RELEASE.jar:na]
at org.springframework.data.elasticsearch.core.MappingBuilder.mapEntity(MappingBuilder.java:137) ~[spring-data-elasticsearch-2.1.3.RELEASE.jar:na]

有什么想法吗?

经过多日的研究,我找到了解决方案,所以我想与社区分享,也许它对其他人也有用。

为避免 WhosebugExpcetion,当 Spring Data Elasticsearch 尝试映射您的递归模式时,您必须在 @Field 注释中使用 ignoreFields 属性,因此映射器将不要进入无限循环。

这是我的 MailFolder class 目前的样子:

...
public class MailFolder {

@Field(type = FieldType.String, index = not_analyzed)
private String id;

@Field(type = FieldType.String, index = not_analyzed)
private String name;

@Field(type = FieldType.String, index = not_analyzed)
private String icon;

@Field(type = FieldType.Boolean, index = not_analyzed)
private boolean system;

@Field(type = FieldType.Nested, ignoreFields = {"children"})
private List<MailFolder> children;
...