Elasticsearch will take any data you throw at it, but without a predefined index, it will try to figure out the data type on its own, which can result in both inefficient storage and querying. It can also limit ways to use your data in some cases.

Let's consider http status codes for example. These values are always integers, however Elasticsearch will treat them like text unless you explicitly define your index.

At Thinkbean, we want to issue a challenge.

We want our clients and prospective clients, developers, partners, and even the competition, to create intention when developing new web properties, apps or digital tools. Yes, there are wonderful digital experiences to be had; we just happen to think all digital experiences should be wonderful.

We are getting excited and packed up to head down to DrupalCon next week. From April 24th - 28th, we will be in Baltimore learning, collaborating, and socializing at the biggest Drupal Community event of the year. As I mentioned, this year the event is in Baltimore, Maryland which is only a 90 minute flight from Boston, our quickest yet to DrupalCon. Well, at least for some of us, looking at you Mike (our Director of Engineering who lives in CA and has amazing weather year round). 

Here are some of the sessions we are really looking forward to:

I run PHP 7 by default on my laptop. For new projects, I typically use Symfony or Drupal 8, and launch the built-in servers with bin/console server:run or drupal server respectively.

For legacy sites that require PHP 5, I have PHP installed in /usr/local/php56/bin and use nginx w/php-fpm to serve them. For these sites, I need to run drush under PHP 5, but PHP 7 is setup as default via the command line.

My solution for this is pretty simple, create an alias named drush5.