Please direct all comments/feedback to PhaniRaj AT Microsoft DOT COM

This is what the editor looks like  :

Let’s start by first creating a connection to your local Hive server.

Once the connection is created, we connect to the Hive server by using the Microsoft ODBC Driver for Hive .
We’ll soon move the console over to use Apache’s new Templeton apis for metadata access and job submission.
You can learn more about Templeton here : http://people.apache.org/~thejas/templeton_doc_latest/

Support for basic Hive Metadata visualization

We visualize the Hive metadata as a hierarchical tree-view .

A query editor for HQL that supports syntax coloring, auto completion and other fun activities.

The IDE hosts an editor that supports auto completion & syntax coloring for HQL keywords & functions.
You can find HQL’s language specification here : https://cwiki.apache.org/confluence/display/Hive/LanguageManual

Clicking on a table name from the above tree view produces a sample query that selects the first 10 rows from the table.  

You can edit this query or clear it and start over.

HQL Code Snippets for common tasks in Hive

We’ve seeded the editor with some code snippets for common tasks .
Below is an example of the “Create External Table” code snippet.

Auto completion  support for hive Functions in the editor.

Auto completion  support for hive keywords in the editor.

About 163 keywords in HQL are supported in the editor.

Metadata sensitive auto completion support for queries.

We inject the metadata we gleaned from the Hive server into the editor so that
you can use intellisense on column names in your queries.

Once you have the query written, hit “Run Query” to kick off query execution.
We kick off the Hive job and wait for its completion, intermittently polling for the results.

Once the query is finished successfully, you will see the query icon light up.

Clicking on the query icon should bring up the results in a tabular format.

If on the other hand, the query failed, you will see a “query failed” icon next to the query.

Clicking on this will bring up a window with links where you can further see details about why the query failed.

In conclusion, I hope this is something that you find useful.
As always your feedback and comments are welcome at my email mentioned above.
There’s many other features that we’re planning for this editor and will post regular updates to this work as we progress.

• WCF Data Services Tools for Windows Store Apps RC
• Visual Studio Asynchronous Programming
• Downloads for Metro style app development

Add new workspace window

Browse collections exposed by an OData Service.

Get first 50 rows from a collection in the OData Service.

Filter by reference navigation properties in the Query Builder menu.

If a type Product has a  1:1 relationship with Categories, you can filter a Products by properties of its
Category.

Clicking on “Edit” next to each row in the grid brings up the edit menu which allows you to :

Edit property values and save to the server .


Edit Raw ATOM for an entity and save to the server

Use this feature to send malformed ATOM payloads to your service and test how the server handles it.

Edit Raw JSON for an entity and save to the server.

Use this feature to send malformed JSON payloads to your service and test how the server handles it.

This bookmarklet is a simple javascript function that changes the contents of standard buttons on Facebook.com.
It changes the "Like" button content to be "Can you Dig it?", unlike to "Stop Digging it", and Comment to "Holler!"

How do I install this bookmarklet ? 

Step 1 : Right-click this link and select "Copy Link address", Bookmarklet link
Step 2 : Open the bookmarklet manager in your browser and add a bookmark with the contents of the above link as the Link Address.
Step 3 : Open up facebook.com and click the bookmark you created in Step 2. 
Step 4 : Profit ! 

You’ll need :
1. Windows 8 Consumer preview and developer tools
2. OData Client library preview for Windows 8 Metro ( Update: Visual Studio 2012 RC has been released and contains an updated version of these assemblies, along with fully-integrated support for Add Service Reference. Install the Ultimate, Professional, or Premium editions on Windows 8 Release Preview to get the update.) .

We’re releasing a preview version of the client libraries for Windows 8 Metro-Style applications to give our users
the ability to create applications that work on Windows 8 .   This client library will work with servers
that comply with the OData v1-v3 protocols. In the blog post below we will describe a sample application
we built and is available for download using this client library.

Step Zero is to generate the client types for the Netflix OData Service using the DataSvcUtil.exe tool.
We haven’t updated the “Add Service Reference”  gesture in Visual Studio 11 yet, so you’ll have to generate the client
types manually .

Here is how you generate the client proxy types for the Netflix OData Service

Open a command prompt as administrator and navigate to %windir%\Microsoft.NET\Framework\v4.0.30128

Run this command :

DataSvcutil.exe /uri:http://odata.netflix.com/Catalog/ /DataServiceCollection /Version:2.0
/out:netflixClientTypes.cs

Copy the generated netflixClientTypes.cs file into the application you create in the next step.

Open Visual Studio 11 > “Create new Project” >”Grid Application”

“Genres” view

To build this view, we will add an “Items Page” and customize the Item template to display
details specific to the “Genre” type in the client types such as “Name”.
We further create a custom property called “TileTitle” which is the first title in the genre,
to see how this is implemented, please consult the ODataSampleViewModel.cs file.
When a user selects a “Genre” we will set the “SelectedGenre” property on the view model
and navigate to the “Titles” screen shown below.

“Titles In Genre” view.

To create this view, we will add another “Items Page” and customize the item template to display details specific to the “Title”
type in the generated client types. To load these titles, we track the selected Genre and call the “LoadTitlesForGenre”
method on the view model with the selected genre.
When a user selects a Title, we navigate to the “TitleDetails” view shown below, with the selected title as a navigation parameter.

“Title Details” view :

To create this view, we add a “Basic page” and customize the layout to show the above content
from the selected title which is passed in as a navigation parameter.

Phani Raj,
Software Design Engineer 2,
OData / WCF Data Services

1. Useful links for OData Server applications : a list of links for debugging/configuring your OData Server application.
2. Useful links for OData Cilent applications : a list of links for using the Data Services client library, DataServiceContext, effectively in your client applications.
3. OData applications I built : Self-promoting set of links for applications I've built which either use OData or enable people to browse OData feeds.

I'm running a short survey to guage interest in an Excel 2007 plugin that reads OData feeds.

Please take this short survey so that I can figure out which scenarios you want to target with this plugin.

Survey link

GenerateDataServiceContext.tt generates a strongly-typed DataServiceContext type based on the service description.

GenerateEntityTypes.tt generates the client-side proxies for entity types exposed by the OData service.

GenerateViewModels.tt ( Silverlight Only ) generates viewmodels based on the entity type and provides some ease-of-use apis.

More documentation coming soon.

The Good :

1. The client library’s events the app depended upon were still present and worked just as well.
2. The OData library had no issues at all with feeds of any kind ( paged/non-paged/with count ) , it worked without a hitch.
3. The databinding classes worked fine for the Phone environment and completion fired events on the right( UI ) thread. 
4. Tombstoning for DataServiceCollection and DataServiceContext works quite well for the rows in the app.
5. The platform is quite nice for debugging on the physical device. Other than some really convoluted tombstoning issues, VS and the debugger chugged along just fine.

The “Needs Improvement”:

1. The DataServiceCollection.LoadAsync<T> api doesn’t return an IAsyncResult when you call it.The reason this is important is because  the marketplace’s certification requirements state that long running network tasks need a “Cancel” button. And the way to cancel a request made by the OData client library is to call CancelRequest on the DataServiceContext instance being used by the app. Since I was using DataServiceCollection in my app and kicking off requests using the LoadAsync and LoadNextPartialSetAsync apis, I couldn’t cancel the current request without a rewrite. Finally, I had to stop using the LoadAsync API on the collection and moved to using DataServiceContext.BeginExecute<T> which does return an IAsyncResult and I could CancelRequest when the UI shows the “Cancel” button.
2. No Credentials support via UseDefaultCredentials and Credentials properties on the DataServiceContext  type. This prevented me from adding support in the app for authenticated services.
3. The emulator is slow on my laptop, I may have to buy a new laptop if I want to use the emulator for developing apps.And here’s a joke for sticking so far with this blog post.
    How slow is it ?
    It’s so slow that the January update for the Phone will be released by the time the emulator starts.

I am looking for other perspectives on developing apps for the marketplace with the OData client library.
How do you find developing with the client library on the Phone ?
What are your pet peeves ? and What are the top features you love ?