Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get API: Allow to specify which fields to load #65

Closed
kimchy opened this issue Mar 17, 2010 · 1 comment
Closed

Get API: Allow to specify which fields to load #65

kimchy opened this issue Mar 17, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Mar 17, 2010

The Get API currently returns the _source. The API should allow to supply fields that will be returned (if stored). By default, the source would still be returned if no fields are specified.

@kimchy
Copy link
Member Author

kimchy commented Mar 17, 2010

Get API: Allow to specify which fields to load, closed by 6243f4f.

rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
Example below. I set the type as text/plain but it is identified as text/html.

```sh
#!/bin/sh

echo "\n\n Delete testidx \n"
curl -XDELETE "http://localhost:9200/testidx"

echo "\n\n Create index and mapping \n"
curl -XPUT "http://localhost:9200/testidx" -d'
{
  "mappings": {
    "session": {
      "properties": {
        "Content": {
          "properties": {
            "content": {
              "type": "attachment",
              "path": "full",
              "store": "yes",
              "fields": {
                "content": {
                  "type": "string",
                  "store": "yes"
                },
                "author": {
                  "type": "string",
                  "store": "yes"
                },
                "title": {
                  "type": "string",
                  "store": "yes"
                },
                "name": {
                  "type": "string",
                  "store": "yes"
                },
                "date": {
                  "type": "date",
                  "format": "dateOptionalTime",
                  "store": "yes"
                },
                "keywords": {
                  "type": "string",
                  "store": "yes"
                },
                "content_type": {
                  "type": "string",
                  "store": "yes"
                },
                "content_length": {
                  "type": "integer",
                  "store": "yes"
                }
              }
            }
          }
        }
      }
    }
  }
}'

echo "\n\n Index document \n"
curl -XPOST "http://localhost:9200/_bulk" -d'
  {"index":{"_index":"testidx","_type":"session"}}
  {"Content":[{"_content_type":"text/plain","content":"BASE64ENCODED_CONTENT"}]}
'

echo "\n\n Refresh \n"
curl -XPOST "http://localhost:9200/testidx/_refresh"

echo "\n\n Get doc type \n"
curl -XPOST "http://localhost:9200/testidx/_search?pretty" -d'
{
  "fields": ["Content.content.content_type","Content.content.content_length","Content.content"]
}'
```

Closes elastic#65.
(cherry picked from commit 38075dc)
maabernethy pushed a commit to maabernethy/elasticsearch that referenced this issue Mar 20, 2017
ywelsch pushed a commit to ywelsch/elasticsearch that referenced this issue Jun 4, 2018
A consequence of elastic#63 is that a FailedToCommitClusterStateException is no longer
thrown by ZenDiscovery#publish(), it is just passed to the listener, so tests
that relied on catching it can no longer work.
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
This track defines an index template that defines common settings. When
bulk-indexing, indices will be automatically created based on this index
template. Therefore, explicit invocation of the create index API are
obsolete (unless they contain additional instructions such as creating
an alias).

With this commit we remove all these tasks and also related tasks (e.g.
it is not necessary to check for cluster health based on a specific
index if that index is not present yet).
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
…stic#65)

This is the initial commit for the Media Manager CloudFront CDN

* This is the inital commit for the Media Manager CloudFront CDN.

We are using terraform to create a CloudFront CDN, with each
sandbox S3 Bucket as an origin server for the CDN.  It routes
traffic to the origin server based on the URL path, so the S3
bucket will need to have the content in the /sandbox S3 folder.

The terraform resource 'aws_cloudfront_distribution' includes
a 'cf_create' var to determine if the CDN should be created, so
this must be passed as true to create the CDN.  Additionally, it
includes a 'cf_enabled' var that must be true for the CDN to
accept traffic.

In the event both of these are true, it will add a tag 'MediaCDN'
to the engageli instance, with the value of the CDN FQDN.  The
rc.local on the engageli instance has also been modified to get
this tag, and if the tag exists will modify the 'storagebaseurl'
in the media manager local.yml file, so when playing video clips
the content will be served via the CDN.  If the tag is not set,
the 'storagebaseurl' will continue to point directly to the S3
bucket as it is today.
modified:   aws/ams-cluster-v1-tf/main.tf
new file:   aws/ams-cluster-v1-tf/media-manager.tf
modified:   aws/ams-cluster-v1-tf/variables.tf
modified:   instance-files/engageli/etc/rc.local

* Added CDN DNS alias 'stack-name-cdn.domain'
modified:   aws/ams-cluster-v1-tf/main.tf
modified:   aws/ams-cluster-v1-tf/media-manager.tf
modified:   aws/ams-cluster-v1-tf/variables.tf

* Implement workaround for terraform bug causing origin servers
to be dropped and added on each apply.
modified:   aws/ams-cluster-v1-tf/media-manager.tf
modified:   aws/ams-cluster-v1-tf/variables.tf

* additional fixup and todo's
modified:   media-manager.tf

* Fixed case where CDN not created, to not create DNS for alias
modified:   aws/ams-cluster-v1-tf/main.tf
modified:   aws/ams-cluster-v1-tf/media-manager.tf

* Changes to address review feedback.
modified:   aws/ams-cluster-v1-tf/main.tf
modified:   aws/ams-cluster-v1-tf/media-manager.tf
modified:   aws/ams-cluster-v1-tf/variables.tf

* Merge branch 'master' of bitbucket.org:engageli/devops into dev/rich/add-media-manager-cdn-2021.02.25

modified:   admin-tools/package-lock.json
modified:   admin-tools/package.json
modified:   aws/ams-cluster-v1-tf/main.tf
modified:   aws/ams-cluster-v1-tf/variables.tf
modified:   packer/tag_all.sh
modified:   provisioning/provision-dequeue.sh

* Changed default for var.cf_cert_arn to production wildcard for
*.p1.engageli-prod.com
modified:   aws/ams-cluster-v1-tf/variables.tf

* fixed missing curly bracket after merge
modified:   aws/ams-cluster-v1-tf/variables.tf

Approved-by: Gideon Avida
emilykmarx pushed a commit to emilykmarx/elasticsearch that referenced this issue Dec 26, 2023
Added support for routing parameters.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant