Skip to content

ElasticPress 1.7
Compare
Choose a tag to compare
@tlovett1 tlovett1 released this 11 Dec 16:07
· 7929 commits to develop since this release
1.7
8632f86

ElasticPress 1.7 restructures meta mapping for posts for much more flexible meta queries. The post_meta Elasticsearch post property has been left for backwards compatibility. As of this version, post meta will be stored in the meta Elasticsearch property. meta is structured as follows:

  • meta.value (string)
  • meta.raw (unanalyzed string)
  • meta.long (unanalyzed number)
  • meta.double (unanalyzed number)
  • meta.boolean (unanalyzed number)
  • meta.date (unanalyzed yyyy-MM-dd date)
  • meta.datetime (unanalyzed yyyy-MM-dd HH:mm:ss datetime)
  • meta.time (unanalyzed HH:mm:ss time)

When querying posts, you will get back meta.value. However, if you plan to mess with the new post mapping, it's important to understand the intricacies.

The real implications of this is in meta_query. You can now effectively search by meta types. See the new section in README.md for details on this.

1.7 also contains the following bugs/enhancements:

  • (Bug) Prevent missed post indexing when duplicate post dates. Props lukaspawlik
  • (Bug) Complex meta types are automatically serialized upon storage.
  • (Enhancement) Index posts according to post type. Props sc0ttkclark
Assets 2
Loading