Significance of order of field in Google App. Engine’s BigTable index

Asked By 0 points N/A Posted on -
qa-featured

Is the order of a field in Google App. Engine’s BigTable index significant, and if so, why? Is it not important with the case of MongoDB’s index buildings? What is the procedure for using SLiM- Scala, Liftweb+mongoDB with .NET?

SHARE
Best Answer by Clair Charles
Best Answer
Best Answer
Answered By 15 points N/A #110458

Significance of order of field in Google App. Engine’s BigTable index

qa-featured

Hallo Marise Rosheen,

To use SLiM- Scala, Liftweb+mongoDB with .NET, you will use the following procedure for them to work:

  • You will first need to install it, and then run it. When you execute it, it places a small program in the task bar of your windows the bottom right side that runs from there.
  • You thus be needed to click on that icon which you see in the task bar and then it will bring a window.
  • In the window you can choose either to start and stop either MongoDB, the SBT or the PHP program which is used by the RockMongo.
  • Still in the window, you can browse the site by clicking on the browser button, and you can also locate the liftweb port which is 8080 in the window.

Hope this helps.

__

Regards
Clair Charles

 

Answered By 20 points N/A #110459

Significance of order of field in Google App. Engine’s BigTable index

qa-featured

Hi there,

Google Application engine has some protocols so it can maintain its performance over the net. So the order of a field in Google Application engine’s (BigTable index ) is significant. But it is totally controlled by Google developer’s team. It is like this because of its security issue.

The procedure of MongoDB’s index buildings with using SLiM- Scala, Liftweb+mongoDB is not a common nethod. It’s quite different from others. So here I am not giving any example of it. I am giving a link of the official page on Scala on .Net. (http://www.scala-lang.org/old/node/168). You can visit here and find more information.

Related Questions