-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
188 lines (173 loc) · 12.4 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
<!DOCTYPE html>
<html lang="en"><head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1"><!-- Begin Jekyll SEO tag v2.8.0 -->
<title>a life in search</title>
<meta name="generator" content="Jekyll v4.3.3" />
<meta property="og:title" content="a life in search" />
<meta name="author" content="Henrik Lindström" />
<meta property="og:locale" content="en_US" />
<link rel="canonical" href="https://www.lindstromhenrik.com/" />
<meta property="og:url" content="https://www.lindstromhenrik.com/" />
<meta property="og:site_name" content="a life in search" />
<meta property="og:type" content="website" />
<meta name="twitter:card" content="summary" />
<meta property="twitter:title" content="a life in search" />
<script type="application/ld+json">
{"@context":"https://schema.org","@type":"WebSite","author":{"@type":"Person","name":"Henrik Lindström"},"headline":"a life in search","name":"a life in search","url":"https://www.lindstromhenrik.com/"}</script>
<!-- End Jekyll SEO tag -->
<link rel="stylesheet" href="/assets/css/style.css"><link type="application/atom+xml" rel="alternate" href="https://www.lindstromhenrik.com/feed.xml" title="a life in search" /><script async src="https://www.googletagmanager.com/gtag/js?id=UA-34278256-1"></script>
<script>
window['ga-disable-UA-34278256-1'] = window.doNotTrack === "1" || navigator.doNotTrack === "1" || navigator.doNotTrack === "yes" || navigator.msDoNotTrack === "1";
window.dataLayer = window.dataLayer || [];
function gtag(){window.dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-34278256-1');
</script>
</head>
<body><header class="site-header">
<div class="wrapper"><a class="site-title" rel="author" href="/">a life in search</a><nav class="site-nav">
<input type="checkbox" id="nav-trigger" class="nav-trigger" />
<label for="nav-trigger">
<span class="menu-icon">
<svg viewBox="0 0 18 15" width="18px" height="15px">
<path d="M18,1.484c0,0.82-0.665,1.484-1.484,1.484H1.484C0.665,2.969,0,2.304,0,1.484l0,0C0,0.665,0.665,0,1.484,0 h15.032C17.335,0,18,0.665,18,1.484L18,1.484z M18,7.516C18,8.335,17.335,9,16.516,9H1.484C0.665,9,0,8.335,0,7.516l0,0 c0-0.82,0.665-1.484,1.484-1.484h15.032C17.335,6.031,18,6.696,18,7.516L18,7.516z M18,13.516C18,14.335,17.335,15,16.516,15H1.484 C0.665,15,0,14.335,0,13.516l0,0c0-0.82,0.665-1.483,1.484-1.483h15.032C17.335,12.031,18,12.695,18,13.516L18,13.516z"/>
</svg>
</span>
</label>
<div class="trigger"><a class="page-link" href="/about/">About</a></div>
</nav></div>
</header>
<main class="page-content" aria-label="Content">
<div class="wrapper">
<div class="home">
<ul class="post-list"><li>
<span class="post-meta">Jun 24, 2018</span>
<h3>
<a class="post-link" href="/running-elasticsearch-curator-as-an-aws-lambda-function/">
Running Elasticsearch Curator as an AWS Lambda function
</a>
</h3>AWS Lambda functions can be used to run the Elasticsearch Curator CLI in a serverless way...</li><li>
<span class="post-meta">Jun 2, 2016</span>
<h3>
<a class="post-link" href="/facet-filtering-with-episerver-find/">
Facet filtering with EPiServer Find
</a>
</h3>Sometimes you want to have a facet calculated on just a subset of the result or have multiple facets each being calculated on a different subset of the result...</li><li>
<span class="post-meta">May 21, 2014</span>
<h3>
<a class="post-link" href="/integration-tests-with-protractor/">
Integration tests with Protractor
</a>
</h3>After playing around with Protractor for a while I wanted to create some integration tests where I would bootstrap the entire server/database before each test to get a consistent state to start from in each test. The problem is that we often have to wait for everything to be setup before running the tests...</li><li>
<span class="post-meta">May 12, 2014</span>
<h3>
<a class="post-link" href="/using-protractor-with-coffescript/">
Using Protractor with CoffeeScript
</a>
</h3>I’ve been playing around with AngularJS for the last couple of weeks during my spare time while being on paternity leave (read late at night). I really like the framework and last night I came across Protractor, the end to end testing framework, and for the first time I think I saw some light in the the UI-testing-tunnel and thought I should share some ideas in a couple of posts...</li><li>
<span class="post-meta">Oct 30, 2013</span>
<h3>
<a class="post-link" href="/language-detection-using-elasticsearch/">
Language detection using Elasticsearch
</a>
</h3>A couple of weeks ago I had the privilege to speak at the Elasticsearch Meetup in Stockholm where I did show a slightly tweaked version of the 'language categorizer' I did write about a couple of months ago and would like to share the changes I did (the naive approach wasn’t accurate enough to be presented live in public ;-))...</li><li>
<span class="post-meta">May 2, 2013</span>
<h3>
<a class="post-link" href="/indexing-only-referenced-vpp-files-with-episerver-find/">
Indexing only referenced VPP-files with EPiServer Find
</a>
</h3>The EPiServer Find CMS integration does not index any files stored in the VPP by default. A convention is included in the integration that index files visible in the file manager and it is enabled by setting the VisibleInFilemanagerVPPIndexingConvention on the FilieIndexer conventions...</li><li>
<span class="post-meta">Mar 15, 2013</span>
<h3>
<a class="post-link" href="/nested-filtering-with-episerver-find/">
Nested filtering with EPiServer Find
</a>
</h3>Some have already noticed one of the x2find mebers, Nested2Find, that enables nested object mappings and filtering to the EPiServer Find API. I would like to give a short description of what it does and how it can help you in some filtering scenarios...</li><li>
<span class="post-meta">Mar 8, 2013</span>
<h3>
<a class="post-link" href="/categorizing-using-elasticsearch/">
Categorizing using Elasticsearch
</a>
</h3>I'm fortunate to work at a company that once a month have a 'hack day' when we are allowed to just try out new and crazy ideas. As an advocate of using search for so much more than just the 'search page' I decided to do a small demo of how to use Elasticsearch to do categorization and I wanted to share some of my ideas...</li><li>
<span class="post-meta">Feb 26, 2013</span>
<h3>
<a class="post-link" href="/hierarchical-faceting-with-episerver-find/">
Hierarchical faceting with EPiServer Find
</a>
</h3>A quite common use case of facets is to show a listing of the number of documents in a result for the different categories on the site (quite common is maybe an understatement as this is often the "hello world!" of faceting). A document can occur in maybe one or more categories and this is where your search index really stands out since it doesn’t care if you have one or two categories associated with the document it will return your facet in no time anyway. Sometimes your categories have a hierarchical structure that you want to reflect in your facet...</li><li>
<span class="post-meta">Feb 15, 2013</span>
<h3>
<a class="post-link" href="/time-to-live-with-episerver-find/">
Time to live with EPiServer Find
</a>
</h3>The latest release of EPiServer Find contains, apart for a number of bug fixes, one new feature and that is the ability to set a time to live value on indexed documents. The value is expressed as a TimeSpan and specifies how long the document should reside in the index before it is automatically deleted. This can be really useful if you index documents continuously (say that you index all items that users currently are looking at on your site) but only what to show the latest (i.e. what users are currently looking at on the site) and don’t want to flood your index over time (i.e I don’t care what someone looked at yesterday). Under these circumstances the time to live-feature can really help you by doing that dirty cleanup job that we all hate to to do...</li><li>
<span class="post-meta">Jan 31, 2013</span>
<h3>
<a class="post-link" href="/random-sort-with-episerver-find/">
Random sort with EPiServer Find
</a>
</h3>I’ll continue my series of blog posts today based on “questions I’ve got” with one regarding randomly ordered search results. This can be quite useful if you want to show a subset of a search result and expose the individual result items of the entire result set equally. Say that you for instance have a list campaign products and want to show a limited number of these on the front page but still expose each one of them an equal amount of times to the users...</li><li>
<span class="post-meta">Jan 22, 2013</span>
<h3>
<a class="post-link" href="/searching-dictionaries-with-episerver-find/">
Searching Dictionaries with EPiServer Find
</a>
</h3>EPiServer Find has extensive support for indexing all kinds of objects and types. However the support for dictionaries is a bit limited. I got a question a couple of weeks ago regarding how to search/filter on the keys or values of a dictionary (and not on a specific value for a specific key). The default dictionary support in EPiServer Find doesn’t support this but it is not that hard to achieve...</li><li>
<span class="post-meta">Sep 17, 2012</span>
<h3>
<a class="post-link" href="/adding-fuzzy-filtering-to-the-episerver-find-fluent-api/">
Adding fuzzy filtering to the EPiServer Find Fluent API
</a>
</h3>A few days back I got a question of how to do fuzzy filtering FuzzyQueries and that the core classes in EPiServer.Find had an implementation of this query but that there wasn't a corresponding filter in either Elasticsearch or EPiServer.Find for doing this. However this is quite easily done anyway and it will enable you to do queries like...</li><li>
<span class="post-meta">Aug 22, 2012</span>
<h3>
<a class="post-link" href="/debugging-elasticsearch-in-eclipse/">
Debugging Elasticsearch in Eclipse
</a>
</h3>I’m one of those developers that think that debugging an application is a great way of gaining knowledge about its inner workings, not just for finding problems but also for educational purposes. Elasticsearch is one of my favorite open source projects that I sometime have the pleasure of debugging. The Elasticsearch homepage is not that extensive when it comes to building and running Elasticsearch in Eclipse so I’m giving a short description of how it is done...</li></ul>
</div>
</div>
</main><footer class="site-footer h-card">
<data class="u-url" href="/%20/"></data>
<div class="wrapper">
<div class="footer-col-wrapper">
<div class="footer-col">
<div style="float: left; margin-right: 10px;">
<img class="gravatar" src="https://www.gravatar.com/avatar/3d05909857b53a5001a6c83326d203b3?s=48" style="border-radius: 50%;" />
</div>
<ul class="contact-list">
<li class="p-name">Henrik Lindström</li>
</ul>
</div>
<div class="footer-col">
<p></p>
</div>
</div>
<div class="social-links"><ul class="social-media-list"><li>
<a rel="me" href="https://github.com/lindstromhenrik" target="_blank" title="github">
<svg class="svg-icon grey">
<use xlink:href="/assets/minima-social-icons.svg#github"></use>
</svg>
</a>
</li>
<li>
<a rel="me" href="https://twitter.com/lindstromhenrik" target="_blank" title="twitter">
<svg class="svg-icon grey">
<use xlink:href="/assets/minima-social-icons.svg#twitter"></use>
</svg>
</a>
</li>
<li>
<a rel="me" href="https://www.linkedin.com/in/lindstromhenrik" target="_blank" title="linkedin">
<svg class="svg-icon grey">
<use xlink:href="/assets/minima-social-icons.svg#linkedin"></use>
</svg>
</a>
</li>
</ul>
</div>
</div>
</footer></body>
</html>