{"action":"created","issue":{"url":"https://api.github.com/repos/elastic/elasticsearch/issues/3714","labels_url":"https://api.github.com/repos/elastic/elasticsearch/issues/3714/labels{/name}","comments_url":"https://api.github.com/repos/elastic/elasticsearch/issues/3714/comments","events_url":"https://api.github.com/repos/elastic/elasticsearch/issues/3714/events","html_url":"https://github.com/elastic/elasticsearch/issues/3714","id":19606937,"number":3714,"title":"Support for IPv6 mapping type","user":{"login":"bodgit","id":559268,"avatar_url":"https://avatars.githubusercontent.com/u/559268?v=3","gravatar_id":"","url":"https://api.github.com/users/bodgit","html_url":"https://github.com/bodgit","followers_url":"https://api.github.com/users/bodgit/followers","following_url":"https://api.github.com/users/bodgit/following{/other_user}","gists_url":"https://api.github.com/users/bodgit/gists{/gist_id}","starred_url":"https://api.github.com/users/bodgit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bodgit/subscriptions","organizations_url":"https://api.github.com/users/bodgit/orgs","repos_url":"https://api.github.com/users/bodgit/repos","events_url":"https://api.github.com/users/bodgit/events{/privacy}","received_events_url":"https://api.github.com/users/bodgit/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/elastic/elasticsearch/labels/stalled","name":"stalled","color":"fef2c0"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":24,"created_at":"2013-09-17T10:43:10Z","updated_at":"2015-07-14T21:52:34Z","closed_at":null,"body":"Currently I can't use the ip mapping type as I have fields that can be either IPv4 or IPv6. However, being able to use range queries is really useful but I can't make use of them because I have to treat the field as a string to handle the case when the field contains an IPv6 value.\r\n\r\nObviously this causes extra hassle as storage would then require 128 bits and when searching, range queries using IPv6 addresses shouldn't match IPv4 addresses, unless you're using the ::ffff:d.d.d.d notation, and IPv6 addresses shouldn't match IPv4 range queries at all.\r\n\r\n(I found [this thread](http://elasticsearch-users.115913.n3.nabble.com/Support-for-first-class-IPv6-address-type-td3960748.html) when this has been raised previously)"},"comment":{"url":"https://api.github.com/repos/elastic/elasticsearch/issues/comments/121402857","html_url":"https://github.com/elastic/elasticsearch/issues/3714#issuecomment-121402857","issue_url":"https://api.github.com/repos/elastic/elasticsearch/issues/3714","id":121402857,"user":{"login":"avleen","id":539525,"avatar_url":"https://avatars.githubusercontent.com/u/539525?v=3","gravatar_id":"","url":"https://api.github.com/users/avleen","html_url":"https://github.com/avleen","followers_url":"https://api.github.com/users/avleen/followers","following_url":"https://api.github.com/users/avleen/following{/other_user}","gists_url":"https://api.github.com/users/avleen/gists{/gist_id}","starred_url":"https://api.github.com/users/avleen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/avleen/subscriptions","organizations_url":"https://api.github.com/users/avleen/orgs","repos_url":"https://api.github.com/users/avleen/repos","events_url":"https://api.github.com/users/avleen/events{/privacy}","received_events_url":"https://api.github.com/users/avleen/received_events","type":"User","site_admin":false},"created_at":"2015-07-14T21:52:34Z","updated_at":"2015-07-14T21:52:34Z","body":"I see we're still blocked on Lucene's support for BigInt for this. But that ticket hasn't seen any action in a while either.\r\nAny updates for this @clintongormley? IPv6 is becoming a real thing, so this would be really handy :-)"}}