By using AWS re:Post, you agree to the Terms of Use

Unanswered Questions tagged with Amazon DocumentDB

Sort by most recent
  • 1
  • 12 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

AWS 2dsphere limitation

Hi all, I am using DocumentDB with Mongo support on AWS and we are having documents that include geolocation. We have read the documentation of AWS for mongo support [here](https://docs.aws.amazon.com/documentdb/latest/developerguide/mongo-apis.html) but despite it says that it's supported we are receiving error during the creation of the index. The error we are getting when creating the index is : "*Command createIndexes failed : Index type not supported : 2dsphere*" The c# code that should generate the index is the below : ``` var prefixIndexName = nameof(Account.Address)+"."+nameof(Account.Address.Geolocation); if (!accountCollection.ExistIndex(prefixIndexName+"_2dsphere")) { Console.WriteLine("Seeding Geolocation Geo2DSphere Index ..."); var geoLocation = new StringFieldDefinition<Account>(prefixIndexName); var indexDefinition = new IndexKeysDefinitionBuilder<Account>().Geo2DSphere(geoLocation); var indexModel = new CreateIndexModel<Account>(indexDefinition, new CreateIndexOptions { Background = false }); accountCollection.CreateIndex(indexModel); } ``` The field that we are trying to add in the index is the "Address" and it looks like this : ``` "Address": { "CountryId": number, "PostCode": string, "AddressLine1": string, "AddressLine2": string, "City": string, "State": string, "Geolocation": { "type": "Point", "coordinates": decimal[] // e.g. [xx.xxxxxxx, xx.xxxxxxx] } } ``` The code is working on my local MongoDB installation, so I believe I am missing something to make it run on AWS. Any help you could provide is valuable, thanks in advance for your time!
0
answers
2
votes
33
views
asked 3 months ago

Quicksight Athena - analysis error: "HIVE_UNSUPPORTED_FORMAT: Unable to create input format"

Hello. I'm trying to create an analysis from my DocumentDB instance. I'm using the aws services Glue, Athena and Quicksight. In Glue I have created a connection to the DocumentDB and a crawler for auto creating tables. This works as expected and tables are created and displayed in glue. Even though I specify that the crawler should not give the tables any prefixes, it does add the database name as a prefix. When I look at the Glue catalog in Athena (the default AwsDataCatalog) I do see the database that was created in glue, however it does not show any tables. If I click on edit, it takes me to the correct database in glue which displays the tables that have been created by the previously mentioned crawler. So my first question is **Why doesn't the tables show up in Athena?** This is blocking me from performing queries in Athena. When I go to QuickSight and select the default Athena glue catalog ("AwsDataCatalog") I DO get the tables created by the crawler, and I can create datasets. However, when I try to create an analysis using these datasets, I get the error: ``` sourceErrorCode: 100071 sourceErrorMessage: [Simba][AthenaJDBC](100071) An error has been thrown from the AWS Athena client. HIVE_UNSUPPORTED_FORMAT: Unable to create input format ``` I have looked a bit around and some people said that this error is due to the table properties **"Input format"** and **"Output format"** being empty (which they indeed are for me). I have tried entering almost all the different formats to the table, but I keep on getting the Quicksight error above only now it has the input format at the end ``` HIVE_UNSUPPORTED_FORMAT: Unable to create input format json ``` **So my second questions is** I do not see anywhere in the crawler where I can specify input or output format. Does it have to be done manually? And What are the correct input and output formats for my setup?
0
answers
0
votes
83
views
asked 4 months ago
0
answers
1
votes
27
views
asked 8 months ago
  • 1
  • 12 / page