npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

azure-search

v0.0.21

Published

A client for the Azure Search service

Downloads

1,270

Readme

Build Status

node-azure-search

A JavaScript client library for the Azure Search service, which works from either from Node.js or the browser. The module is browserify compatible.

This module calls the Azure Search REST API. The documentation for the API is available here.

Installation

Use npm:

$ npm install azure-search

Usage

If using from node:

var AzureSearch = require('azure-search');
var client = AzureSearch({
  url: "https://XXX.search.windows.net",
  key: "YYY",
  version: "2016-09-01", // optional, can be used to enable preview apis
  headers: { // optional, for example to enable searchId in telemetry in logs
    "x-ms-azs-return-searchid": "true",
    "Access-Control-Expose-Headers": "x-ms-azs-searchid"
      
  }
});

If using in the browser:

<html>
  <head>
    <script src="azure-search.min.js"></script>
  </head>
  <body>
    <script>

var client = AzureSearch({
  url: "https://XXX.search.windows.net",
  key:"YYYY"
});

    </script>
  </body>
</html>

Note that from the browser, you must have the corsOptions set in the index schema, and only search, suggest, lookup and count will work.

A client object can then be used to create, update, list, get and delete indexes:

var schema = {
  name: 'myindex',
  fields:
   [ { name: 'id',
       type: 'Edm.String',
       searchable: false,
       filterable: true,
       retrievable: true,
       sortable: true,
       facetable: true,
       key: true },
     { name: 'description',
       type: 'Edm.String',
       searchable: true,
       filterable: false,
       retrievable: true,
       sortable: false,
       facetable: false,
       key: false } ],
  scoringProfiles: [],
  defaultScoringProfile: null,
  corsOptions: null };

// create/update an index
client.createIndex(schema, function(err, schema){
	// optional error, or the schema object back from the service
});

// update an index
client.updateIndex('myindex', schema, function(err){
  // optional error
});

// get an index
client.getIndex('myindex', function(err, schema){
	// optional error, or the schema object back from the service
});

// list the indexes
client.listIndexes(function(err, schemas){
	// optional error, or the list of schemas from the service
});

// get the stats for an index
client.getIndexStats('myindex', function(err, stats){
	// optional error, or the list of index stats from the service
});

 var data = {
      'text': 'Text to analyze',
      'analyzer': 'standard'
    }
// shows how an analyzer breaks text into tokens
client.testAnalyzer('myindex', data, function (err, tokens) {
  //optional error, or array of tokens
}

// delete an index
client.deleteIndex('myindex', function(err){
	// optional error
});

You can also add documents to the index, and search it:

var doc1 = {
  "id": "document1",
  "description": "this is the description of my document"
}

// add documents to an index
client.addDocuments('myindex', [doc1], function(err, results){
	// optional error, or confirmation of each document being added
});

// retrieve a document from an index
client.lookup('myindex', 'document1', function(){
	// optional error, or the document
});

// count the number of documents in the index
client.count('myindex', function(err, count){
	// optional error, or the number of documents in the index
});

// search the index (note that multiple arguments can be passed as an array)
client.search('myindex', {search: "document", top: 10, facets: ["facet1", "facet2"]}, function(err, results){
	// optional error, or an array of matching results
});

// suggest results based on partial input
client.suggest('myindex', {search: "doc"}, function(err, results){
	// optional error, or an array of matching results
});

You can get, create, update and delete data sources:

var options = {
	name : "blob-datasource",
	type : "azureblob",
	credentials : { connectionString : "DefaultEndpointsProtocol=https;AccountName=xxx;AccountKey=yyy" },
	container : { name : "mycontainer", query : "" }
}

client.createDataSource(options, function(err, data){
	// data source created
});

client.updateDataSource(options, function(err, data){
	// data source updated
});

client.deleteDataSource("blob-datasource", function(err, data){
	// data source deleted
});

client.getDataSource("dataSourceName", function(err, data) {
  //data source returned
});

You can also create, update, list, get, delete, run and reset indexers:

var schema = {
  name: 'myindexer',
  description: 'Anything', //Optional. Anything you want, or null
  dataSourceName: 'myDSName', //Required. The name of an existing data source
  targetIndexName: 'myIndexName', //Required. The name of an existing index
  schedule: { //Optional. All of the parameters below are required.
    interval: 'PT15M', //The pattern for this is: "P[nD][T[nH][nM]]". Examples:  PT15M for every 15 minutes, PT2H for every 2 hours.
    startTime: '2016-06-01T00:00:00Z' //A UTC datetime when the indexer should start running.
  },
  parameters: { //Optional. All of the parameters below are optional.
    'maxFailedItems' : 10, //Default is 0
    'maxFailedItemsPerBatch' : 5, //Default is 0
    'base64EncodeKeys': false, //Default is false
    'batchSize': 500 //The default depends on the data source type: it is 1000 for Azure SQL and DocumentDB, and 10 for Azure Blob Storage
  }};

// create/update an indexer
client.createIndexer(schema, function(err, schema){
	// optional error, or the schema object back from the service
});

// update an indexer
client.updateIndexer('myindexer', schema, function(err){
  // optional error
});

// get an indexer
client.getIndexer('myindexer', function(err, schema){
	// optional error, or the schema object back from the service
});

// list the indexers
client.listIndexers(function(err, schemas){
	// optional error, or the list of schemas from the service
});

// get the status for an indexer
client.getIndexerStatus('myindexer', function(err, status){
	// optional error, or the indexer status object
});

// delete an indexer
client.deleteIndexer('myindexer', function(err){
	// optional error
});

// run an indexer
client.runIndexer('myindexer', function(err){
	// optional error
});

// reset an indexer
client.resetIndexer('myindexer', function(err){
	// optional error
});

It is also possible to work with Synonym Maps:

var client = require('azure-search')({
  url: 'https://xxx.search.windows.net',
  key: 'your key goes here',
  // Mandatory in order to enable preview support of synonyms
  version: '2017-11-11'
})

var schema = {
  name: 'mysynonmap',
  // only the 'solr' format is supported for now
  format: 'solr',
  synonyms: 'a=>b\nb=>c',
}

client.createSynonymMap(schema, function(err, data) {
  // optional error or the created map data
});

client.updateOrCreateSynonymMap('mysynonmap', schema, function(err, data) {
  // optional error or
  // when updating - data is empty
  // when creating - data would contain the created map
});

client.getSynonymMap('mysynonmap', function(err, data) {
  // optional error or the synonym map data
});

client.listSynonymMaps(function (err, maps) {
  // optional error or the list of maps defined under the account
})

client.deleteSynonymMap('mysynonmap', function (err) {
  // optional error
});

It is also possible to work with Skillsets for Cognitive Search, currently in preview version '2017-11-11-Preview':

var client = require('azure-search')({
  url: 'https://xxx.search.windows.net',
  key: 'your key goes here',
  // Mandatory in order to enable preview support of skillsets
  version: '2017-11-11-Preview'
})

var schema = {
  name: 'myskillset', // Required for using the POST method
  description: 'My skillset description', // Optional 
  skills: [{ // Required array of skills
    '@odata.type': '#Microsoft.Skills.Text.SentimentSkill',
    inputs: [{
      name: 'text',
      source: '/document/content'
    }],
    outputs: [{
      name: 'score',
      targetName: 'myScore'
    }]
  }]
}

client.createSkillset(schema, function(err, data) {
  // optional error or the created skillset data
});

client.updateOrCreateSkillset('myskillset', schema, function(err, data) {
  // optional error or
  // when updating - data is empty
  // when creating - data would contain the created skillset data
});

client.getSkillset('myskillset', function(err, data) {
  // optional error or the skillset data
});

client.listSkillsets(function (err, maps) {
  // optional error or the list of skillsets defined under the account
})

client.deleteSynonymMap('myskillset', function (err) {
  // optional error
});

Accessing the Raw Response

The raw response body is always returned as the 3rd argument in the callback.

i.e.

// search the index
client.search('myindex', {search: "document", top: 10}, function(err, results, raw){
	// raw argument contains response body as described here:
	// https://msdn.microsoft.com/en-gb/library/azure/dn798927.aspx
});

Using Promises

To use promises, invoke azureSearch as a function instead of a constructor.

i.e.

var azureSearch = require('azure-search');
azureSearch({
    url: "https://XXX.search.windows.net",
    key: "YYY"
})
    .then(client => client.listIndexes())
    .then(console.log, console.error)

If you need access to the raw response body, use callback syntax instead.

Contributing

Contributions are very welcome.

To download the dependencies:

> npm install

To build the minified JavaScript:

> npm run build

To run the tests:

> npm run test

Please note that you will have to update your clientConfiguration and storageConnectionString variables in order to run the tests.

License

MIT