Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Failure to properly escape bucket names in index creation.
See original GitHub issueWhen i run ottoman.ensureIndices i get the following error
failed to created neccessary indices { Error: syntax error - at -
at /home/motoko/workspace/heroku/couchbase-api/node_modules/couchbase/lib/bucket.js:668:15
requestID: '5f8eeace-586c-4e4a-8e95-69e7fb1055d8',
code: 3000,
otherErrors: [] }
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
couchbase primary index for bucket with '-' in the name
You simply need to escape the bucket name using backquotes: CREATE PRIMARY INDEX ON `sample-partner`;. It should work that way. Remember to ...
Read more >CREATE INDEX | Couchbase Docs
The CREATE INDEX statement allows you to create a secondary index. Secondary indexes contain a filtered or a full set of keys in...
Read more >Bucket naming rules - Amazon Simple Storage Service
Bucket names must be between 3 (min) and 63 (max) characters long. Bucket names can consist only of lowercase letters, numbers, dots (.),...
Read more >Error Message on indexer console - Splunk Community
name = Bucket Cache ... Data writes to index path '%s'cannot safely proceed. ... message = Failed to create a directory at %s....
Read more >Query unpartitioned data in Cloud Storage | BigQuery
To query external data in a Cloud Storage bucket, you need the following IAM permissions: ... For Table, enter the name of the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I had a similar issue. I had named my bucket
bucket-namewith a hyphen. If you’re creating n1ql indexes, n1ql is going to throw because the hyphen is a reserved character. I corrected this issue by renaming my bucketbucket_name.@AV25242 Ottoman v2 will work fine with
travel-sample; bucket names with hyphen and indexes will be created successfully. I thought it’s was supported by Server or SDK at some time in the past. Now is working ok, I run some test to ensure it.